Project Enterprise Overview Scenario Description

1. Project Enterprise OverviewScenario Description

2. What is Project Enterprise • A Sales oriented Scenario • Implementation engineered to highlight the value propositions of SOA and Process Integration • You will recognize – It’s real life • Industry non-specific • Extensible - supports Cross Capability and Cross Brand • Basis for BDD and SOA/ESB collateral as well • Foundation for STEW and Customer facing materials (Demos, EoTs, PoTs, PoC samples) • Creates Russian Doll effect • Improves Efficiency of Enablement • Once you know the STEW you know the PoTs and Demos

3. JK Enterprises – Project Enterprise • Organization Description • Multiple Market Segments – Mass Market, SMB, Corporate • Multiple Channels – Web, Brick & Mortar, Remote Sales, Back Office • Struggling to grow uniformly at low cost and risk • IT: • Mix of build vs buy – SAP, Siebel, CICS, Batch • Legacy Applications – core accounting, order entry • Multiple Platforms - Windows, AIX, iSeries, zSeries • Heterogeneous topology • Very little reuse of components and skills • Numerous Targets for Business Innovation and Optimization (BIO) but no methodology nor way forward

4. JK Enterprises – IT Implementation • Today • 200+ Developers • 20+ different development tools • No end-end methodology • Lacking governance model • About to embark on major development supporting Business Innovation and Optimization effort • Tomorrow • Better linkage with business • Supporting methodology with artifacts and contracts defined • Supported and integrated tools • Role based • Business participates

5. JK Enterprises Challenge #1 – Account Open • Account Sales: • Latency – customers want to use their accounts right away • Incomplete Status available during setup process – can’t answer customer questions • Inconsistent response on completion or when issues arise • Lack of collaborative materials to ease pre-sale (chat, co-browsing, difficult to ‘find’ information) • Limited sales channels • Account Application: • Complex application forms • Different applications for different products • Errors due to re-keying of information from paper application to screen • Lack of single customer view • Account Verification: • Lack of digital imaging • Lack of single customer view • Declining too many customer requests • Lack of dynamic, rules-based pricing • Credit checks inconsistent, expensive, and time consuming • Account Activation: • Prolonged process due to lack of digital signature • Manually entering information in various internal systems (CRM, ERP, etc.)

6. Account Open – Business Goals • Strategic Initiative - Optimize Account Setup • Reduce Cost and Latency – grow efficiently and profitably • Improve sales and customer service through increased speed and responsiveness • Enhance productivity through reductions in total cost of ownership (TCO) • Increase the value and reach of services and products • Reduce risk and increase consistency via rules based Business Process Management

7. JK Enterprises Account Open Process Overview

8. Account Open – Account Verification Use Cases • Customer information is verified • Retrieve Credit Report if necessary • If credit score is “bad”, additional documentation is required • Based on customer profile (and credit score), pricing plan is calculated • Manual application review, depending on score • Generate decline or proceed to Account Activation step

9. Observation Model Project Enterprise - How ? Rational RequisitePro WebSphere Business Modeler WebSphere Integration Developer Choreograph services using BPEL, WSDL, etc. Create Observation Model with KPIs & export to Monitor Create, Simulate & Analyze As-Is Business Model Configure Human Task Manager (including Ad-Hoc) & Client Create, Simulate, Analyze and Optimize To-Be Business Model Integration Developer BPEL WSDL BusinessAnalyst Use Business Rules, State Machines, Web Services, Adapters, ESB, etc. WSDL Create FinancialReports & ROIEstimates • Runtime • WebSphere Process Server • WebSphere Portal Server • WebSphere Business Monitor UML Model Relational Database Schemas Create & Manage SystemRequirements Test Deploy and Test WSDL EAR Run Trace Requirements & Create System Use Case Realizations RDB Mapping Model & Implement Services, & expose as Web Services UML Develop Portlets Rational Data Architect 4Q05 Monitor Administration Rational Software Architect Data Architect Portal Developer Business Operations Analyst J2EE Developer Architect Run-time Statistics

10. Project Enterprise – IT Solution Topology

11. Project Enterprise – A complex Use Case

12. You will Build this Use Case this week • From Demos to the Labs – just a matter of more detail • Hands-on experience with the IBM Software Development Platform • WebSphere Business Modeler • Rational Software Architect (RSA) • WebSphere Integration Developer • Introduction to Rational’s ADLC stack: ClearQuest, Requisite Pro and ClearCase • Build, Deploy and Test a BPEL-based composite application to J2EE and SOA platform: WebSphere Process Server using IBM’s Software Development Platform • Execute Business Driven Development which is both Contract- and Role-based

13. Logistics of the Project Enterprise Environment • Runs on VMware • Reduced performance than a “real” machine • Totally self contained environment • Tools • Eclipse 3.0 based • Starting workspaces have assets already developed for you • Windows XP environment • Scripts are provided • Step by step instructions • You will leave with it in your hands and enabled to apply it • More to come – we are just getting started