Airline Oellermann Melton 11022007 SOA

Airline SOA: The Impact of SOA in the Travel Industry Mike Melton Chief Architect EDS Corporation William Oellermann Technology Director Microsoft Corporation Agenda Services Oriented Architecture as a Business Enabler Integration Modernization SOA In Production Architecture Availability Performance Keys to a successful SOA Commitment Governance Enterprise Viewpoint Architecture Experience Monitoring Services Oriented Architecture as a Business Enabler Key IT Issues of the Airline Industry Historical way to rigidity – how much longer can I live with it? Manageability – Complexity increases year over year – the “hairball” effect Inflexibility – Applications are silo’d, difficult to connect and lack an end-to-end customer view Risk – Increases directly with the aging of the “legacy language” workforce and the inflexibility of the integration & interfacing. Costs – Increases due to higher maintenance and development needs of old platforms and languages Time to Market – slow reaction time The Enterprise Customer Interaction Challenge Level 1 – Siloed Optimization Business Units Level 2 – Aggregated Optimization Customer Ops Revenue Shared “Inside View” Optimizing the Internal Business Processes “Outside View” Optimizing the Real-Life Processes from a Customer Perspective Level 3 – Cross-Functional Optimization Customer Ops Revenue Shared Irregular Operations Schedule Change Customer Data Update Enterprise Integration Requires Agility Agile Solutions based on a Service Oriented Architecture enable new solutions to be developed deployed rapidly Interoperability Standard based components make IT systems more flexible and significantly simplifies integration Reuse Reduces development cost and time and increases quality of future applications Streamlined Architectures and Technology Solutions Provides consistency and maximizes repeatability with the adoption of industry standards and a common technology Leveraging Legacy Investment Incorporates legacy systems as part of the solution potentially lowers development cost while preserving robust functionality and intellectual capital SOA can be a critical enabler for companies to effectively respond to challenging market dynamics and capitalize on new business opportunities and achieve agility Application Modernization: Overview Why application modernization.. Today’s solutions have to change. Building up and around current legacy applications is running out of value Business needs to keep moving. An airline cannot afford to put the business at a stand still while waiting for a new solution The business cannot be put at risk. Changing PSS solutions can be a risky event if not planned and managed correctly Need to improve time to market for new opportunities because the airline must grow and change now. What is application modernization.. A well defined process to move from legacy technology to a new modern solution in a low risk environment that can provide immediate and continued benefits Provides multiple go forward options in a single solution environment that include build, partner and re-factor in a custom or utility environment Is a business driven change that requires a strong understanding of the business processes in order to determine which are to be maintained and which changed Application Modernization Modernization is a multi-year process that revitalizes IT assets to enable the enterprise to rapidly respond to changing market conditions in a highly efficient manner. Desired State EDS has created assets to support Modernization of airline applications: Industry Frameworks Documented Business Processes Future Business Perspective SOA Blue Print Re-tire Re-place Re-Architect Re-Interface Re-Host Re-Factor Re-Learn Our Modernization Strategy guides the actual work from assessment through build and into deployment. EDS Reservations Services Architecture 1.2 Shop Product Offerings 1.4 Purchase/ Sell Product Offering 1.5 Travel 1.6 Execute Post Travel Functions 1.2 Shop Product Offerings 1.4 Purchase/ Sell Product Offering 1.5 Travel 1.6 Execute Post Travel Func tions 1.7 Manage Customer Communications Trading Partners B2B Customer Employee Internal Systems Airline Middleware (optional) EDS Reservation Services (OTA + EDS Standards v3.1) Utility Services Services Oriented Application Development EDS Reservations Embedded Solutions Enabled Solutions Ticketing Refund / Re Issue Misc. Documents Seat Maps IROP (New) Point Solutions Compatible Solutions (examples) Customer Data Fares Shopping Sales IROP Customer Mgmt. Departure Control Baggage Load Control Schedules Availability Inventory Robotics 1.7 Manage Customer Communications Trading Partners B2B Customer Employee Internal Systems Airline Middleware (optional) EDS Interface Services (OTA + EDS Standards v3.1) Utility Intelligent Services Services Oriented Application Development EDS Reservations Embedded Solutions Enabled Solutions Ticketing Refund / Re Issue Misc. Documents Seat Maps IROP (New) Point Solutions Compatible Solutions (examples) Customer Data Fares Shopping Sales IROP Customer Mgmt. Departure Control Baggage Load Control Schedules Availability Inventory Robotics Airline SOA 2 May 2006 page 2 • EDS Confidential Current State Reservations DCS Fares An Airline Example of SOA in Production How did EDS Address the Opportunity? The solution required a strong mix of business and technology knowledge with global delivery capabilities Strategy – EDS’ developed a strategy and funded the effort to create an offering to assist airlines with business transformation and legacy modernization and architecture capabilities Managed Process – EDS’ developed a methodologies for application’s modernization and business transformation Global Capabilities – Acquired, trained and built out global assets to execute Enterprise Solution – Designed an architecture solution to work for all business processes of a company Technology Partners – EDS’ established strong partnership and relationship for key components of the solution EDS Reservations – Selected as the application to stand up and deploy as both a proof of concept and a means to modernize our reservation capabilities EDS Modernization Program 2005 Airline BATOG Airline Frameworks Process & Data Models 2006 2007 2008 - 2012 Transformation Modernization Architecture Airline SME’s Fares Tools Reservations Plan Flight Operations Maintenance, Repair & Overhaul Enterprise SOA Design Client Specific SOA Rel. 1 SOA Rel. 2 Flight Ops Rel 1 SOA Rel. 3 EDS SOA Road Map 2005 2006 2007 GUI / Portal 2008 2009 B2B Framework 2010 SHARES Adapter Interface Services Modernization Development Services Utility Services axsRes/Control Adapter Pub / Sub Fares Adapter Web Service Mgr Web Services Message Bus ODS Rules Engine Orchestration Testing Services Web Services R2 Completed In Progress Planned Logging Security Monitoring R2 Security R2 Business Int. Security R3 BAM Data WH EDS Airline SOA: Architecture And Tools Legend Release 1 Release 1 Presentation Layer GDS OA Gov’t .com PDA Kiosk GUI Intranet RA RM Ops OPS Trading Partners Trading Partners Customer 1.2 Shop Product Offerings 1.4 Purchase Sell Product Offering Employee 1.6 Execute Post Travel Functions Internal Systems 1.7 Manage Customer Communications B2B Release 2 Release 2 1.5 Travel Interface Services Release 3 Web Services Web Services and Portals Message Bus Message Bus Web Services Mgmt Web ServicesMgmt Security Security and Utility Services Client Business Intelligence Development Environment Monitoring Monitoring and Data Warehousing Integrated Applications EDS Application Data Mgmt Web Services Orchestration Rules Technology in this space will depend on the application. i.e. EDS Fares SOA Application Central Database Midrange Application Legacy Application Embedded Solutions Applications Airline-Specific (examples) Customer Data Enabled Solutions Shopping Robotics Operational Concepts Environmental management is an architect principal, not an implementation detail Individual servers are considered sacrificial. Loss of individual servers is expected and extraordinary means to protect an individual server aren’t taken. N+1 deployment methodology. If two servers are required to support production volume and still have failover, three servers (N=2, +1) will be deployed to provide for planned maintenance and break-fix support without an outage. Component consistency. Servers and other components are chosen based on operational class, not specific deployment, to each initial selection and deployment and aid redeployment within operational class as needed. SOA Management Portal Airline Application Owners Microsoft Portal Application Developers Airline Service Owners SOA Management Portal SOA Support Team Portal Users Portal Users LG Portal LG Console Admin System Center Enterprise Sys Mgmt System Center Console FTP Server Admin GUI Storage Mgmt Network Mgmt Infrastructure Mgmt SST Console SOA Platform Management Toolset … Cute GUI Emulator FrontPlane TIBCO EMS A ACTIONAL LG S ACTIONAL SST S T S T T Microsoft T S IIS ORACLE DB A Admin T S T S T Schedule .Net . T A S DCS S WCF/WF T S FTP Server Reservation Point Solutions SOA Systems Environment Legend Portal Access Portal Integration Email / SMS Alerts Primary Msg Flows Horizontal SOA Mgmt Vertical SOA Mgmt SOA Auditing SNMP Traps (Apps-level) Systems Management A T S ACTIONAL Ghost Agent TIBCO Hawk Agent System Mgmt Agent A Client Migration Project Featuring SOA Situation Major US airline, after a merger, needed a reliable interface between res/airport operations Interfaces were created for movement of the Res data using the web services through the EDS Airline SOA Adapters were created via SOA to the flight operations system for on-going data movement Results Migration of data went smoothly On-going data movement continues flawlessly System performance has exceeded expectations Project completed in less time due to SOA and one third the costs of legacy one-off interface alternative EDS Airline SOA: Architecture And Tools Legend Presentation Layer GDS OA Gov’t .com PDA Kiosk GUI Intranet RA RM Ops OPS Release 1 Trading Partners Trading Partners Customer Employee Internal Systems B2B Release 2 1.2 Shop Product Offerings 1.4 Purchase Sell Product Offering 1.5 Travel 1.6 Execute Post Travel Functions 1.7 Manage Customer Communications Interface Services Release 3 Web Services and Portals Message Bus Web Services Mgmt Security and and Utility Services Client Business Intelligence TBD Monitoring and and Data Warehousing TBD Development Environment EDS Application Data Mgmt Data Integrated Applications Rules Rules Technology in this space will depend on the application. i.e. EDS Fares Mgmt Web Services Web Services Orchestration Orchestration SOA Application Central Database Midrange Application Legacy Application Embedded Solutions Applications Airline-Specific (examples) Customer Data Enabled Solutions Shopping Robotics Key Development Constructs Industry Knowledge Transportation Industry Framework Industry Trends and Market Forces IT Governance / Policies Industry Frameworks Building New Applications Legacy Seat Map Application Composite Seat Map Services Interface Services 5.1.2 Assign Orchestration Confirm Seating 5.1.2.1 Verify 5.1.2.2 5.1.2.1 Change Assigned SeatAssign SeatAssigned Seat Web Services Development Environment Business Rules Premium Seat Rules Exit Seat Rules Rul es Operational Data Store Data Access Services Business Governance Business Processes Workflow Interfaces • • • • • • Information and Data Models Application / Solution Components Technical Infrastructure Tools Techniques Concepts Reference models Architectures Best practices Logic Application Server Communications Enterprise Service Bus Seat Map Data Security Utility Services Database Enterprise Information Management Strategic Information Architecture Client-Specific Dynamic Business Model Data Security Alternate Resource Allocation Scenarios Strategic Insight • Composite for maximum Reuse • State of the art tools • Maximum flexibility Enterprise Information Architecture Client-Specific Enterprise Data Model Client-Specific Information Services Single View of Truth Single Point of Integration Airline Frameworks: Foundation for Airline Solutions Application Development Evolves to Business Process Programming Functionality will be derived directly from the client’s business processes. Client’s Business Processes EDS will utilize our Industry Frameworks for process modeling. EDS Industry Frameworks 1.2 Shop Product Offerings 1.4 Purchase Sell Product Offering 1.5 Travel 1.6 Execute Post Travel Functions 1.7 Manage Customer Communications Process Modeling EDS will perform the process orchestration, Using Business Process Execution Language, That will utilize the appropriate calls from the Action Library, To perform the client’s business functionality. Development Environment A B C G F D E F G H Business Process Programming D A B Services Library New Construction Approach Legacy Seat Map Application Composite Seat Map Services Interface Services 5.1.2 Assign Orchestration Confirm Seating 5.1.2.1 Verify 5.1.2.2 5.1.2.1 Change Web Services Assigned Seat Assign Seat Assigned Seat Development Environment Business Rules Premium Seat Rules Exit Seat Rules Application Server Communications Rules Operational Data Store Workflow Interfaces Data Access Services Logic Enterprise Service Bus Seat Map Data Security Utility Services Data Security Microsoft Proof of Concept Goals Demonstrate proposed Microsoft architecture: Running OTA messages Comments Achieved 300 TPS @ about 75% box utilization Microsoft committed to import and export about the end of 2007. Phase 1 Scalability Performance BPEL import and export Demonstrate ability to develop services using: Orchestration Phase 2 .Net Development Rules Web Services Management The product direction for Microsoft WSM is unclear. EDS will continue to monitor for future use. Demonstrate performance and reliability against TPF Phase 3 Run 8 hour endurance test Run volume test to 100 TPS Configuration in Charlotte required multiple tests. Achieved 96 TPS in volume test, limited by SHARES test system. Logical Testing Environment Phase 1 – Microsoft Performance Test Function Name Simultaneous Calls 4 2 1 4 2 1 4 2 1 4 2 1 4 2 1 Time In Call Avg. (ms) 27 12 10 19 8 7 28 13 10 38 18 11 47 21 14 Req/Sec Avg. 132 131 78 186 177 107 130 127 80 97 95 70 80 86 61 Total Requests 41,291 41.022 24,293 57,751 55,108 33,407 40,281 39,313 24,787 30,208 29,764 21,792 27,832 28,522 20,342 MutateAvailability MutateAvailability MutateAvailability GetRandomCalcKey GetRandomCalcKey GetRandomCalcKey GetSQLData GetSQLData GetSQLData StoreAvailability (Sync) StoreAvailability (Sync) StoreAvailability (Sync) RequestAvailability RequestAvailability RequestAvailability Phase 2 - Ability to create services 1. Windows workflow rated very high. 2. Windows Business rules engine met requirements. 3. Visual Studio is easy to learn. 4. A business rules expert should be added to the teams. 5. Microsoft support was excellent Phase 3 - Performance against TPF Results 1. Over the 8.5 hours of endurance test execution 2,032,525 transactions executed. 28 errors Error rate of .001378% 2. Ran a 1 hour stress test ramping up to 96 TPS. Limited by the TPF Test System CPU usage 8% .71 Second response time 3. Difficulty setting up the test because of connectivity and firewalls. Not a tool issue. Airline SOA Trend Analysis – Message Volume Message Volume – Community SOA 32,000,000 30,925,017 31,806,139 30,236,469 24,000,000 21,590,831 22,655,321 16,000,000 11,040,925 8,000,000 2,461,369 70,146 116,799 5,732,294 6,237,290 0 Sep-06 Oct-06 Nov-06 Dec-06 Jan-07 Feb-07 Mar-07 Apr-07 May-07 Jun-07 Jul-07 • 70,000 messages to 32 Million messages a month and growing • Used by 10 Airlines Keys to a Successful SOA Keys Support the Business Commitment Architecture Testing Monitoring Common Services Team Governance Enterprise Viewpoint Experience Designed for RunTM Why “Designed for RunTM” is Critical in a SOA Environment Cost (TCO) Poorly designed SOA implementation will drive run costs up SOA A multi-year modernization roadmap is critical and requires an end-to-end governance model Client Server “Designed for RunTM” Mainframe Build Run Time “Proliferation of poorly designed, redundant services causes IT chaos that may exceed the costs and complexity of the systems being replaced.” - Gartner Create a Common Services Team Application Services Common Business Components, i.e. credit card authorization Security, i.e. Authorization & Authentication Utilities, i.e. date and time Data Services Enterprise Data Stores Data Access Services Meta-Data Repository Integration & Control Services Web Services Management Event Management Registration Orchestration Specialized Services Availability Workload Management Capacity Planning Interface Services UI Framework Interface Gateways, i.e. DMZ, FTP Translation Instrumentation Services Journaling/Logging Alert and Error Handling Audit Control EDS SOA Governance Model To minimize the risks and costs associated with SOA, EDS has developed an SOA governance model to provide the framework for planning, developing, implementing, and supporting a secure, reliable SOA environment Operations Management Business Process Management Configuration Management Requirements Management Registry/ Repository Management SOA Governance Model Architecture Planning Services Life Cycle Competency Center Management Security Management Lessons Learned Things to Change Changes (effort and philosophy) to traditional data center operations environment were more extensive than original estimated Do not under estimate governance. We are still working on getting it right Needed more and more detailed organizational education Integrating multiple Best of Breed Things that Worked Performance and availability are maturing much faster than anticipated Scope of applicable projects and early benefits was greater than expected The “Legacy Team” is now sold that this is the future Summary SOA is a long-term, strategic commitment that requires a multi-year funding commitment ROI will be long term Best initiated in conjunction with a large modernization effort SOA has three critical phases or components 1. A well thought through design 2. Knowledge of the tools (vendor relationships) 3. Engineering and execution of the operations environment Alignment to the business is critical to success Process model Business knowledge of the value of SOA Thinking of services v. green screen © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.