2 Identifying the roadmap to SOA helped us develop the roadmap towards the final vision Agile IT-BusinessServices-based ProcessesSpeedEfficiencyCustom fitSOA Value Add32Services-based PortalsOrchestrate services into business processesData Exposing Services1Consolidate services into composite applications providing 360 viewsTraditional Development and IntegrationShare information with multiple consumersTime
3 SOA Step #1 Consists of exposing enterprise information to internal or external “client” applicationsData Exposing ServicesExample: Product Shipping Status1External Service ConsumersInternal Service ConsumersCustomer A ProcurementCustomer B ProcurementSales PortalCustomer ServiceFirewallThe most common use of Web Services today: exposing data to a variety of consumer applications.It is easy to see why this is attractive: Web Services provide a single, standards-based, way of providing information to any consuming application.The business case is simple.On the cost side: a small overhead of building a re-usable service.On the benefit side:The more applications – the greater the benefitThe more these applications change over time – the greater the benefitThe more diversity in these applications’ platforms – the greater the benefitGet_Shipment_ Status ServiceA single, universal method for making information available to multiple consuming applications independent of their platformERPeBusinessClient ServerPackaged Applications
5 Services-based Portals Get_Support_Call_History Sales Force Automation Step #2 Consists of creating portal applications that create “360 Degree” views of their users work environmentServices-based PortalsExample: A Sales Portal2FirewallConsolidation of services into a “composite application” or portal creating 360 views of a user’s world360 Sales PortalGet_Customer_NewsGet_Order_StatusGet_Support_Call_HistoryTrack_QuotaGet_LeadsThe second step: the creation of 360 degree portal applications: composite apps that consolidate all the services that are relevant to a specific user.The steps are:Expose information as web servicesConsolidate the relevant services in portals for a specific audience.Depiction of the particular example on the slide:Here you see a portal for a sales person – it consolidates services that expose information from a variety of sources, internal and external: for example, you get you Order Status from the ERP system, some news about your client from Factiva, the latest customer support status from the Call Center application etc.The business case:On the cost side: the overhead of creating the servicesOn the benefit side: the availability to share these services among several different portals and create these portals very easily without much business logic required – e.g., on this slide, the Get_Order_Status service may be published to a Sales Portal, but can also be a part of an Executive Portal, a Customer Service Portal, a Order Management Portal, a Self-Service Portal, etc…ERPCall CenterSales Force AutomationMarketing AutomationeBusinessClient ServerPacked Applications
6 Composite Applications OUR SECOND GENERATION SOA: SERVICES TO INTEGRATE THE ENTERPRISE AND BUILD COMPOSITE APPLICATIONSComposite Applications Assembled from Business Services Components and Portlets that Expose Enterprise Data and FunctionalityComposite ApplicationsServices PortalSales PortalEmployee Manager PortaleSupport“Traditional” Portal ApplicationsGet_CustomerGet_CustomerOpen_CaseCreate_QuoteGet_HistoryGet_ContractEnterprise Infrastructure ServicesShared Business ServicesPortal ServicesEnterprise Service BusShared Application ServicesEnterprise ServicesEnterprise ApplicationsEnterprise DataCustomersProducts, etc.Search, Content Mgmt, etc.ERP, CRM, etc.
7 It allows us to build powerful new business applications. Superior Customer InsightBetter Coordination and Sharing Among Selling TeamIntegration of Selling (what we promise) with Delivery (what the customer experiences)
8 The new architecture and many of the same services can enable customer facing applications. 360 degree view of my relationship with BEAImproved coordination with BEA and my team membersReduced productivity losses
9 Our SOA approach has helped us create big wins for our Business at a very rapid pace Renewals06/0303 /04Knowledge Express03/04eLicense03/0303/04HR Portal08/02Dev2Dev03/0203/0306/03eOrders05/02eSupport12/0111/026/03Enterprise Infrastructure Services (EIS)Enterprise Applications (ERP, SFA, etc.)
10 Benefit Examples: Impact on BEA’s eBusiness Program Enterprise Architecture increases IT proficiency and optimizes business valueBenefit Examples: Impact on BEA’s eBusiness Program$5.5 M savings in application development$2.2 M savings in supporting functions (production environment support, application support, etc.)EfficiencySpeed50% reduction in development time for new applicationsMost releases in 4 months: 12x4 Development Model50,000+ development man-hours delivered with less than 3% schedule varianceOver $20M implementation costs within 1% of budgetPredictabilityFor the IT organization, the benefits of our architecture were many. It helped us dramatically improve our delivery track record: we build a lot faster, better and cheaper than 2 years agoIt also improved the quality of the service we provide our businessFinally, as a CIO, I am always looking for ways to improve the skills and institutional knowledge of my organization. Creating an architecture with standard technologies and solutions certainly helped us develop deep skills and that is a key to productivity.Quality &PerformanceAll apps released with zero known functional defectsAlways on infrastructureIP and SkillsDepth of skills/institutional knowledge in standards based architecture and technologies.
11 STEP #3 IS ORCHESTRATING SERVICES INTO BUSINESS PROCESSES Services-Based ProcessesExample: A Solution Milestone Invoicing Process3Verify Product Shipment StatusVerify Project Milestone StatusGet Services Burn RateMap Against Contract TermsValidate Status with CustomerCreate InvoiceBusiness ProcessService OrchestrationGet_Contract_Burn_RateGet_Shipment_StatusHere is step 3 : the creation of Services –based Processes.Here the steps are as follow:Expose functions as web services across any applicationWeave them together (or orchestrate them) using a Business Process Manager or workflow engine into an overall business process – this is something you can do using BEA’s Workshop product for example.Here is an example of a process that cuts across multiple applications that can be enabled nicely with an SOA. In this example, we are looking at invoicing process. This process is a little more complex than you would normally have it because it is about invoicing for a Solution offering which is a combination of Hardware, Software, Professional Services. For example, this could be a Call Center Telephony solution, or a new CRM application, etc.To invoice such a solution, the company must use a milestone invoicing approach, billing its customer upon completion of certain project milestones. The process requires the company to check and validate the status of a number of activities: status of shipment, status of the integration project, as well as check upon the terms that were agreed upon with the customer. The process cuts across many applications.The key to the benefit of this approach is the ease of working with the Web Services which requires only modest skills compared to alternative approaches. Another benefit you can anticipate is the use of a common language for IT and Business: having a discussion with a business analyst about “Get_Shipment_Status” is fairly easy.Get_Milestone_StatusGet_TermsGet_Customer_ValidationCreate_ InvoiceShipping - ERPProfessional Services AutomationContract ManagementCustomer PortalBillingeBusinessClient ServerPackaged Application
12 THE NEED FOR “A” IN SOAOpportunities for Architectural Standards and Shared ServicesPortal 1Portal 2 …… Portal iService 1Service 2Service 3Service 4Service nEnterprise-wide Shared Services or StandardsMessaging – Service Directory and Brokering – QoS Management - Application and Database Connectivity – Security – Data Matching – Meta Data Management – Profile Management - Single Sign On, etc.App 1App 2 …… App P
13 THE SIMPLE IDEA FOR BEA’S FUTURE APPLICATION ARCHITECTURE Streamlined Core Processes Accessed by Role-Based WorkbenchesInternal WorkbenchExternal WorkbenchSalesServicesMarketingSupportCustomersPartnersNew Customer AcquisitionOpportunity to CashServices DeliveryEnterprise KnowledgeSharing
14 Role Based Portals Shall Leverage IT Investments Made Across the Entire Application Portfolio High re-use of common ServicesReuse of Infrastructure/Foundational ComponentsReduction in time needed to develop new capabilitiesShared Infrastructure / Business ServiceSpecific Services (limited or no re-use)
15 As This Future Vision Is Deployed, BEA’s Legacy Applications Are Dramatically Simplified Market AnalysisDemand GenerationLead MgmtOpp.MgmtQuoteMgmtOrder MgmtFulfillmentCustomerServiceRIPKana / eMA / Sales Rep hierarchyeOrdersSiebelPeoplesoftRIPKnowledge ExpressRenewalseLicenseRIPPartnerNetAPAC-specific appsRIPClarify / eSupportDev2DevXLSRIPQuikQuoteRIPEval.Manual Export ComplianceEntitlementsDLCRIPRenewals - XLSRIPRIPCustDBRIPEval.Credit CheckACT! / XLSDRSmySupportRevDBRIPLead XLSRIPManual contractsTRIPRIPExtensityRIPEducation.bea.comSales & Marketing PortalRIPBugDBCommerce.bea.comSales AnalyticsRIPCalladusRIPXLSRIPCustomer RepositoryNOT FINALBEAMROCKSRIP