Integration Hub

1
 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

2
 Integration Hub Overview
Solution Internal Benefits
The Integration Hub provides Customers Users Suppliers Partners Leveraging the
an end-to-end integrated Integration Hub asset
solution for the Communications helps businesses:
and High Tech Industry Fundamental Data
• Assure quality data
featuring the best of breed Architecture Requirement • Reduce costs
packaged systems for: Frameworks • Improve revenue
• CRM Process
Data assurance
Conversion
• Billing Models
Rules
• Decrease order
Business
• Provisioning Events processing time
Using EAI middleware, the
Integration Hub offers: Leveraging the
• Fundamental Architecture Integration Hub asset
Best of Breed Packaged Systems enables development
Frameworks
efforts to:
• Data Requirements
• Reduce work effort
• Data Conversion Rules • Lower cost
• Business Events Order Order Billing Provisioning Inventory Fulfillment • Lower risk
Entry Mgmt. (Internal) (Internal) Mgmt. (Shipper)
• Process Models (Web) (Internal) (Suppliers) • Improve quality

3
 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 Billing

Sales Message Guiding &

Customer Usage Proc. Rating
Taxation
Self Service
Quotes /
Web Customer Trouble Order Invoicing & Accts
Care Ticketing Mediation Collections
Gateway Creation Format Rec.

Order Customer
Managemen Database Mgt
t Other
Order Mgt Suppler External
Customer Product Interfaces
Gateway
Activation / Svc Assurance
OSS Order Print
Svc Activ. Interconnect Services
Task Mgt Test Mgt
Mgt

Provisioning Banks /
Workforce Network Lockbox
Config. Mgt Enterprise Management
Mgt Mgt
Design / Inventory GL/AR/AP
HR
Assign Mgt Cash Mgt Credit Card
Trouble Supplier
Maint. Mgt Fault Mgt Asset Mgt Purchas’g
Mgt DB

4
 Enterprise Application Integration (EAI)
Definition of EAI:
A set of technologies Customers Internal Users Suppliers Partners
that enables the
integration of end- Connector Connector Connector Connector
to-end business
processes and data
(information) across “Integration Hub”
disparate
applications to Connector Connector Connector Connector Connector Connector

increase an
organization’s ability
to respond and Order Order Billing Provisioning Inventory Fulfillment
adapt to change. Entry
(Web)
Mgmt.
(Internal)
(Internal) (Internal) Mgmt.
(Suppliers)
(Shipper)

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

5
 EAI Value Proposition
Business Drivers for EAI
Increase timeliness  Access Customer Data Real Time - Fully integrated, up-
and accuracy of to-the-second visibility and control of the business and
information customer experience
 Improve Data Accuracy - Reduce multiple data entry
Increase return on tasks, eliminating errors
technology investment  Respond to Change Faster - Create a more nimble
interface to internal and external packaged, custom,
Enhance collaborations legacy, and web applications
with partners
 Enhance Customer Experience - Help to create a
Manage ubiquitous customer-centric organization
interactions (supplier’s  Extend Enterprise Focus - Integrate packaged, custom
suppliers and and legacy applications and assimilate disparate systems
customer’s customers)  Decrease SI and Operating Costs - Significantly decrease
long term development and maintenance time and
Handle Mergers and increase reusability
Acquisitions  Connect with Business Partners - Enable B2B
transactions
Address Regulation
and Deregulation
 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.

7
Integration Hub Architecture Components
Application Architecture Components Application Connectors
• Drivers provide pre-built interfaces to packaged
CRM Billing applications (can also be custom-developed if
needed)
• Transformers use Event Transformation Rules
that translate from specific APIs into the
Driver Driver Driver Driver common Shared Object Model format (includes
field mapping, translation, and validation rules)
Transformer Transformer Integration Transformer Transformer
Hub • Publish/Subscribe components send business
Publisher Subscriber Publisher Subscriber events to/from the Communicator messaging
infrastructure
Communicator Channel
Infrastructure
Shared Object Model
Architecture Process Models
• Process Automation provides the mechanism to
Publisher Subscriber Publisher Subscriber automate business rules and processes
Transformer Transformer Transformer Transformer
Common Architecture
Driver Driver Driver Driver • Shared Object Model provides a predefined
Process Automation common logical model of communications
industry business objects & events
Provisioning
Legend: • Communicator provides transactional
EAI Provided synch/asynch messaging infrastructure
Accenture
Developed • Channel Architecture defines how messaging
will be partitioned for high-performance
Integration Hub
communications
8
 What is the Integration Hub?
 Software – designed, coded, tested
 Pre-configured versions of best of breed 3 rd-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

9
Myths and Facts about the Integration Hub
Myth Fact
This is COTS This is not packaged software— client
(custom off-the-shelf
software) receives all the source code and documents;
no maintenance agreements required

This is nothing more than The solution includes customizations,

packaged applications modifications, and additions to the
installed out of the box packaged applications to bring business
value to the software implementation

This is a specific client Communications industry thought-leadership

implementation turned conceptualized and designed the solution to
into an asset have common events that support a wide
variety of communications clients

This solution is static and Asset is continually updated with new

will become outdated software versions and current market trends

10
 Order to Cash Process

This process
details the
Create Sales &
Customer
Create
Customer

Customer Account
interaction Care
Account
starting from  Customer Account
customer and Data is Translated into
Integration Hub Order Information
order creation is sent for Billing
through service Enterprise  Receipt of Order
Application Information is Billing
activation to
Acknowledged
billing Integration
 
Order Status Details Process Automation
Routed to Process Model Sends Order to Provisioning

 
Generate Order Worktasks
 Network Operations Center
Personnel Updates Manual Tasks Inventory
Management
Network Complete Automated Tasks
Elements
Update Automated Tasks
 Provisioning


11
 Why BizTalk Server?
We are
 Up-and-coming / Emerging EAI product
capitalizing on our  Strong Relationship / Alliance between
Accenture and Microsoft
strategic alliance
with Microsoft  Process-Based EAI
to delivery  Ease of Development
Microsoft based  Standards for Interoperability
Solutions  XML
 B2B standards
to our clients  Industry XML support
 Architectural Integration
 Scalability
 Manageability
 Platform 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 Ability
and ISVs may accelerate the to
consolidation of the integration Execute
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 Completeness of Vision

Companies will probably need to

run more than one integration
broker vendor within their
enterprise. 2
1
Source: GartnerGroup Strategic Analysis Report
September 2000 (R-11-5113)
2
Source: GartnerGroup Application Integration Conference
May 2001
13
 Integration Hub BizTalk Solution
Microsoft BizTalk Platform: 3 Business Events BizTalk Orchestration
 Create Account - transfer the  Routes Data between
 BizTalk Server
account hierarchy from CRM to Applications
2000
Billing.
 Siebel  Add Service Instance - create a
eCommunications new service instance (level at
2000 which usage will be captured) to
be billed.
 Portal Infranet
6.1  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 HTTP Transport
BizTalk OOB
2000
COM Call
Config and/or Code Application
Application
Workflow
Workflow

ASP Receive
Integration Hub – BizTalk
Page

Process Data Structure Messaging Document Operations

Automation Transformation Definition Configuration Tracking Management

Exception
Business Data Entity
Transformation Record Handling
Processes Definition Message Routing
Rules Correlation Logging &
3 Business Events Data Validation
Notification

Call Portal
COM API

Custom Wrapper

Portal
Infranet
6.1

15
 Value Proposition
Business
Assure High  Decrease errors in systems caused by
Quality Data duplicate entry

Reduce  Reduce cost of maintaining OSS system

Long-Term Costs interfaces and staffing

Improve  Generate more revenue through immediate

Revenue Assurance and accurate billing

Reduce  Decrease order detail collection effort and

Order Processing improve lead time for service activation
Time

16
 Value Proposition
Project Development
Reduce Work Effort  Saves between 1000-2500 workdays of
design, build, and integration work. Quick
time-to-market

Lower Cost  Asset build costs are shared across clients

which allows clients to realize business
capabilities without starting from scratch

Lower Risk  Solution is proven with several successful

client implementations

Convenience  Develop in solution center environment,

utilizing deep CRM, Billing, Order
Management and EAI expertise

17
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

Sales &
This process Customer Care
details the  
interaction
starting from 
customer
account and
order creation EAI
to billing 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 Development Development Accenture
Software Foundation Blueprint Knowledge Capital

Reusable software Integration Hub Integration Hub Accenture

components development assets based planning and experience in the
include: include: development areas of:
• Common • Common methodology • Service Providers
Foundation Classes Development include: Processes
• Common Channel Toolset • Analysis • Product Vision
Event Classes • Design Framework • Design • Integration
• Application • Version Control • Build & Test Experience
Connectors for Tools • Project • Extensive Vitria
Data • Performance Management Experience
Transformation Designs • Work-effort
• Process Models • Etc. Estimation
• Enterprise A major component
Application of this design is the
Customizations “cross application
data design”
22
 Development Foundation
Integration Hub Development Development Accenture
Software Foundation Blueprint 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 Development Blueprint
Integration Hub Development Development Accenture
Software Foundation Blueprint Knowledge Capital

Project and Program Management

• Estimating Models • Development Methodology • Work Planning Templates

Capability Build and Assembly and

Capability
Release Component Product Test
Analysis
Design Test

• Business • Interface • Transformation Class • Test Approach

Requirements Descriptions Model • Test Cycles
• Common Data • Business Event • Object Models & • Test Conditions
Mapping Definitions Detailed Designs • Expected Results
• Account & • Connection Model • Class Detailed Designs • Test Scripts
Product Definitions • Coded modules
Integration • Architecture • Component Test
Approach Framework Cycles/Conditions
Approaches and • Component Test Scripts
Guidelines
24
 Integration Hub Knowledge Capital
Integration Hub Development Development Accenture
Software Foundation Blueprint Knowledge Capital

Communications Industry Process Experience

 Communication industry process models for specific functional areas
and services (i.e. Service Providers processes)
Product Vision Based on Industry Experience
 Support broadband, narrowband, and wireless services
BSS/OSS Integration Experience
 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