Integration Hub

Agenda
  

Accenture Communication Integration Hub Overview Enterprise Application Integration (EAI) Overview Integration Hub Solution Architecture  Microsoft BizTalk Server EAI Platform Comparison Value Proposition Credentials Appendix: Accenture Methodology & Supporting Slides

   

Integration Hub Overview

Solution
The Integration Hub provides an end-to-end integrated solution for the Communications and High Tech Industry featuring the best of breed packaged systems for: CRM Billing Provisioning Using EAI middleware, the Integration Hub offers: Fundamental Architecture Frameworks Data Requirements Data Conversion Rules Business Events Process Models
Internal Customers Users Suppliers Partners

Benefits
Leveraging the Integration Hub asset helps businesses: Assure quality data Reduce costs Improve revenue assurance Decrease order processing time Leveraging the Integration Hub asset enables development efforts to: Reduce work effort Lower cost Lower risk Improve quality

Fundamental Architecture Frameworks Process Models

Data Requirement Data Conversion Rules

Business Events

Best of Breed Packaged Systems

Order Entry (Web)

Order Mgmt. (Internal)

Billing (Internal)

Provisioning Inventory Fulfillment (Internal) Mgmt. (Shipper) (Suppliers)

The Integration Challenge

Enterprise applications have traditionally been integrated using numerous point-to-point interfaces that can be difficult and expensive to maintain and manage.
Customer Management Customer Self Service
Web Gateway Customer Care Sales Trouble Ticketing Quotes / Order Creation

Billing Usage
Mediation Message Proc. Invoicing & Format Guiding & Rating Collections Taxation Accts Rec.

Order Managemen t
Order Mgt

Customer Database Mgt Suppler Gateway

OSS Interconnect Customer Product Order

Other External Interfaces

Print Services Banks / Lockbox Credit Card

Activation / Svc Assurance

Task Mgt Svc Activ. Mgt Workforce Mgt Test Mgt

Provisioning
Config. Mgt Design / Assign Inventory Mgt Trouble Mgt

Network Mgt

Enterprise Management
GL/AR/AP Cash Mgt Asset Mgt Supplier DB HR Purchas g

Maint. Mgt

Fault Mgt

Enterprise Application Integration (EAI)

Definition of EAI: A set of technologies that enables the integration of endto-end business processes and data (information) across disparate applications to increase an organization s ability to respond and adapt to change.
Customers Internal Users Suppliers Partners

Connector

Connector

Connector

Connector

Integration Hub

Connector

Connector

Connector

Connector

Connector

Connector

Order Entry (Web)

Order Mgmt. (Internal)

Billing (Internal)

Provisioning (Internal)

Inventory Mgmt. (Suppliers)

Fulfillment (Shipper)

By 2004, the market for EAI products & services will grow to over $30 billion 28% of total expenditures on integration - Ovum
5

Business Drivers for EAI Increase timeliness and accuracy of information Increase return on technology investment Enhance collaborations with partners Manage ubiquitous interactions (supplier s suppliers and customer s customers) Handle Mergers and Acquisitions Address Regulation and Deregulation

EAI Value Proposition



 

  

 

Access Customer Data Real Time - Fully integrated, upto-the-second visibility and control of the business and customer experience Improve Data Accuracy - Reduce multiple data entry tasks, eliminating errors Respond to Change Faster - Create a more nimble interface to internal and external packaged, custom, legacy, and web applications Enhance Customer Experience - Help to create a customer-centric organization Extend Enterprise Focus - Integrate packaged, custom and legacy applications and assimilate disparate systems Decrease SI and Operating Costs - Significantly decrease long term development and maintenance time and increase reusability Connect with Business Partners - Enable B2B transactions Enable Web Access - Enable customer self service and eCommerce and web based access for internal use
6

Why Did Accenture Create an EAI Asset?



Communications clients were facing same integration challenges over and over. Integration architecture and foundation are similar for every client. We saw an opportunity for reuse and leverage. Clients were time-constrained to implement integrated systems to go-to-market quickly. We wanted to provide a competitive differentiator to attract clients by offering a lower cost solution.

Integration Hub Architecture Components

Application Architecture Components
CRM Billing

Application Connectors
Drivers provide pre-built interfaces to packaged applications (can also be custom-developed if needed) Transformers use Event Transformation Rules that translate from specific APIs into the common Shared Object Model format (includes field mapping, translation, and validation rules) Publish/Subscribe components send business events to/from the Communicator messaging infrastructure

Driver Transformer Publisher

Driver Transformer Subscriber

Driver

Driver Transformer Subscriber

Integration Hub
Shared Object Model

Transformer Publisher

Communicator Infrastructure Publisher Transformer Driver Subscriber Transformer Driver

Channel Architecture

Process Models
Process Automation provides the mechanism to automate business rules and processes

Publisher Transformer Driver Process Automation

Subscriber Transformer Driver

Common Architecture
Shared Object Model provides a predefined common logical model of communications industry business objects & events Communicator provides transactional synch/asynch messaging infrastructure Channel Architecture defines how messaging will be partitioned for high-performance communications
8

Provisioning

Legend: EAI Provided Accenture Developed Integration Hub

What is the Integration Hub?

 

Software

designed, coded, tested

Pre-configured versions of best of breed 3rd-party software Development framework - methodology and templates Customized data mapping between applications Extensible and scalable architecture Business events and process models designed for the communications industry Configurable for clients needs Proven solution

   

 

Myths and Facts about the Integration Hub

Myth This is COTS (custom off-the-shelf software) This is nothing more than packaged applications installed out of the box This is a specific client implementation turned into an asset This solution is static and will become outdated Fact This is not packaged software client receives all the source code and documents; no maintenance agreements required The solution includes customizations, modifications, and additions to the packaged applications to bring business value to the software implementation Communications industry thought-leadership conceptualized and designed the solution to have common events that support a wide variety of communications clients Asset is continually updated with new software versions and current market trends

10

Order to Cash Process

This process details the interaction starting from customer and order creation through service activation to billing
Sales & Customer Care
Customer Account Data is Translated into Integration Hub Create Customer Account

Create Customer Account

Enterprise Application Integration

Order Status Details Routed to Process Model Generate Order Worktasks Network Operations Center Personnel Updates Manual Tasks

Order Information is sent for Billing Receipt of Order Information is Acknowledged

Billing

Process Automation Sends Order to Provisioning

Network Elements

Inventory Management Provisioning

Complete Automated Tasks

Update Automated Tasks

11

Why BizTalk Server?

We are capitalizing on our strategic alliance with Microsoft to delivery Microsoft based Solutions to our clients
    

Up-and-coming / Emerging EAI product Strong Relationship / Alliance between Accenture and Microsoft Process-Based EAI Ease of Development Standards for Interoperability
  

XML B2B standards Industry XML support Scalability Manageability Platform Integration

Architectural Integration
  

Lowest Cost (fully functional) EAI Product Available software license fees

12

BizTalk Industry Analysis

[Microsoft s] clout is such that it influences the integration middleware market even before its products are shipping. 1 Microsoft's customary strategy of low software prices and strong promotion with software developers and ISVs may accelerate the consolidation of the integration broker market during the next several years. 1 Some departments and business units will want or require BizTalk Server, even when another broker may have been previously purchased. 2 Companies will probably need to run more than one integration broker vendor within their enterprise. 2
1

Ability to Execute

Completeness of Vision

Source: GartnerGroup Strategic Analysis Report September 2000 (R-11-5113) Source: GartnerGroup Application Integration Conference May 2001 13

Integration Hub BizTalk Solution

Microsoft BizTalk Platform:


BizTalk Server 2000 Siebel eCommunications 2000 Portal Infranet 6.1

3 Business Events  Create Account - transfer the account hierarchy from CRM to Billing.


BizTalk Orchestration  Routes Data between Applications

Add Service Instance - create a new service instance (level at which usage will be captured) to be billed. Add Product- start billing for a new product or product set. a debit or credit to a billing account

14

Integration Hub BizTalk Conceptual Design

Legend

Siebel 2000
Workflow

HTTP Transport COM Call

BizTalk OOB Config and/or Code Application

ASP Receive Page

Integration Hub

BizTalk

Process Automation

Data Transformation

Structure Definition

Messaging Configuration

Document Tracking

Operations Management

Business Processes 3 Business Events

Transformation Rules

Data Entity Definition Data Validation

Message Routing

Record Correlation

Exception Handling Logging & Notification

Call Portal COM API

Custom Wrapper

Portal Infranet 6.1

15

Value Proposition
Business
Assure High Quality Data Reduce Long-Term Costs


Decrease errors in systems caused by duplicate entry Reduce cost of maintaining OSS system interfaces and staffing

Improve Revenue Assurance Reduce Order Processing Time

Generate more revenue through immediate and accurate billing Decrease order detail collection effort and improve lead time for service activation

16

Value Proposition
Project Development
Reduce Work Effort


Saves between 1000-2500 workdays of design, build, and integration work. Quick time-to-market Asset build costs are shared across clients which allows clients to realize business capabilities without starting from scratch Solution is proven with several successful client implementations Develop in solution center environment, utilizing deep CRM, Billing, Order Management and EAI expertise
17

Lower Cost

Lower Risk

Convenience

Appendix

18

Key Experiences and Lessons Learned



EAI team and application teams should communicate at developer and team lead levels Staff application subject matter experts on the EAI teams Verify field value translations between applications; e.g. failure to identify what the cancel reason value should map to from CRM to billing Develop restart/recovery capabilities for failed business events Prioritize the processing of business events; e.g. CreateAccount event is processed before ModifyAccount event Validation of field values in EAI should only be done in the applications

 

 

19

Order to Cash Process

This process details the interaction starting from customer account and order creation to billing
Sales & Customer Care

EAI Microsoft BizTalk

Billing

20

BizTalk Process Details

New customer account is created in Siebel via Customer Sales Rep. Customer s order is captured and sent for fulfillment. Customer Account data, represented as an XML message, is brought into BizTalk Server and transformed into the Integration Hub's business event data structure. Additional order details -- service instance and products -- are subsequently processed BizTalk orchestration sends customer account and order details to Portal Infranet for billing via the Portal Application Integration Component (AIC). Acknowledgement of information received is sent back to BizTalk via Portal AIC.

21

Integration Hub Assets Framework

Integration Hub provides both software and non-software assets that are critical for solution development
Integration Hub Software Development Foundation Development Blueprint Accenture Knowledge Capital

Reusable software components include:

Common Foundation Classes Common Channel Event Classes Application Connectors for Data Transformation Process Models Enterprise Application Customizations

Integration Hub development assets include:

Common Development Toolset Design Framework Version Control Tools Performance Designs Etc.

Integration Hub based planning and development methodology include:

Analysis Design Build & Test Project Management Work-effort Estimation

Accenture experience in the areas of:

Service Providers Processes Product Vision Integration Experience Extensive Vitria Experience

A major component of this design is the cross application data design

22

Development Foundation
Integration Hub Software Development Foundation Development Blueprint Accenture Knowledge Capital

Cross Application Data Design

Mapping of data entities (Account, Product, Order) across all business events. Definition of common events across CRM and Billing

Design Framework
  

Transformation Framework - Java class hierarchy design to custom coding the business rules for message transformations Error Logging - Guidelines for when to implement error logging and a common log message format Exception Handling - Using the Error Diagrams to define when to stop the connection model, re-start the connection model after a period of time and when to abort a message Acknowledgement - Common definition for acknowledgement messages, both successful and unsuccessful

23

Integration Hub
Integration Hub Software Development Foundation

evelopment Blueprint
evelopment Blueprint Accenture Knowledge Capital

Project and Program Management

Estimating Models Development Methodology Work Planning Templates

Capability Analysis
Business Requirements Common Data Mapping Account & Product Integration Approach

Capability elease esign

Interface Descriptions Business Event Definitions Connection Model Definitions Architecture Framework Approaches and Guidelines

Build and Component est

Transformation Class Model Object Models & Detailed Designs Class Detailed Designs Coded modules Component Test Cycles/Conditions Component Test Scripts

Assembly and Product est

Test Approach Test Cycles Test Conditions Expected Results Test Scripts

24

Integration Hub Knowledge Capital

Integration Hub Software Development Foundation Development Blueprint Accenture Knowledge Capital

Communications Industry Process Experience



Communication industry process models for specific functional areas and services (i.e. Service Providers processes) Support broadband, narrowband, and wireless services Knowledge of end-to-end solutions required at service providers Extensive experience with best of breed/ relevant packaged applications software Extensive experience with BizTalk Lessons learned from prior Siebel, Vitria, Clarify, Portal Infranet, Arbor integrations
25

Product Vision Based on Industry Experience



BSS/OSS Integration Experience