1. art and entertainment
2. visual art and design
3. architecture

BT (Global Services)
Transforming to SOA
Agenda
• Introducing BT Global Services
• Context & Business Challenges
• Integration Strategy
• SOA Design Evolution
• Evolving SOA Delivery
• Accomplishments
• Exploiting SOA
• The Next Level
• Conclusion
BT’s Connected World & Global Services
• BT is one of the world’s leading providers of communications solutions
serving customers in Europe, the Americas and Asia Pacific
• Principal activities : IT & networking services, local, national &
international telecommunications services, & higher-value broadband
and internet products and services
• BT Global Services:
–
operates in more than 130 countries
– It provides networked IT services to meet the needs of multi-site
organisations globally.
– It serves 80% of FTSE 100, and 19 of top 20 UK headquartered financial
institutions
– BT Global Services revenue is growing at 8-10% per annum
Agenda
• Introducing BT Global Services
• Context & Business Challenges
• Integration Strategy
• SOA Design Evolution
• Evolving SOA Delivery
• Accomplishments
• Exploiting SOA
• The Next Level
• Conclusion
Business Change Drivers - Agility
• Integrate US and EU subsidiaries & acquisitions : urgent need to
rationalise operations & systems
• Handle increasingly complex consumer / supplier / partner
relationships
• Address multiple product lines, business processes, customer
channels
• Reduce manual intervention leading to data integrity issues
• Retain customer loyalty by making customer experience simple
and complete
The Standard Operating Environment
(SOE) Proposition
• For BT Global Services to Create Cost Competitive Advantage
with Consistency and Satisfy Customers requires:
– A Common Product Portfolio
–
Supported by Common Business Processes
–
Supported by a standard set of Systems/Tools
“SOE is the largest transformation project in our industry”
Andy Green, CEO BTGS
Agenda
• Introducing BT Global Services
• Context & Business Challenges
• Integration Strategy
• SOA Design Evolution
• Evolving SOA Delivery
• Accomplishments
• Exploiting SOA
• The Next Level
• Conclusion
The SOE Terrain
• Tight budgetary constraints
• Legacy of EAI false starts :
– Confidence issues :too complicated, too expensive, why EAI?
– Delivery crisis : needed to catch up fast with the rest of the programme
• Severe skills shortage - Integration / J2EE skills
• No integration architecture : Thin lines between boxes
• Integration Legacy - developers invented their own protocols
and did p2p using hub and spoke : “worst of both worlds”
Action Plan
• Recruit the right type of people (technical enthusiasts) rather
than skills match (minimum = some Java background)
• Generous training budget (to incentivise)
• Early uplift to BEA WLI 8.1 - more suited to rapid delivery
• Strong partnership with BEA to
– produce an architectural blueprint fit for SOE (BIA)
– run a de-risking programme to identify issues early
• Instilled a ruthless delivery ethos
BEA WLI 8.1 Drivers
• Enabled BT to fast track SOA - Planned for 18 months hence
• Easier connectivity to EIS’s - Decreased dependence on COTS
vendors for expensive adapters + reduced SI costs
• Portal, Web Services and EAI under one umbrella: common
skills re-using common components in a single IDE
• Skill efficiencies: Able to combine 3 roles (transformation (XSLT)
specialist, J2EE developer, process designer) into one
• Flexibility of the toolkit enabled rapid delivery
Agenda
• Introducing BT Global Services
• Context & Business Challenges
• Integration Strategy
• SOA Design Evolution
• Evolving SOA Delivery
• Accomplishments
• Exploiting SOA
• The Next Level
• Conclusion
Business Integration Assessment (BIA)
A partnership between BT and BEA PS to deliver:
• A SOE Hub architecture blueprint
• A framework for designers to achieve
–
Reuse
–
Productivity
–
Reduction of support and maintenance costs
• A recommended delivery strategy (“steel threads”)
… Incorporating BEA WLI 8.1 best practises
… Incorporating learning from other BT Hubs
BTGS Integration Evolution
Central BEA Integration Platform (Hub)
Stage 4
Service Oriented
Architectures
Stage 3
Process Integration
Stage 2
Structural
Integration
Stage 1
Point to Point
Integration
Pre Integration
Stand-alone
systems with few
interfaces
“Stovepipe”
processes with
little organisational
reuse
Manual re-entry &
synchronisation of
data between
applications
Point to point
custom interfaces
using API’s or data
synchronisation
tools
Message oriented
middleware creates
loosely coupled
systems
But, custom code
leads to tightly
coupled systems
Leverages Level 2
interface architecture
as commodity
Interface architecture
deployed as hub and
star or message bus
Information between
systems is not just
shared – it is
managed
Middleware includes
message brokers or
application servers
Middleware includes
process automation
modelling tools
Middleware features:
data transformation
rules processing
transaction integrity
Middleware features:
workflow modelling
automated routing
automated decisions
Enterprise Application
Interface Model exists
Enterprise Business
Model exists
Leverages EAI
enabled applications
from first stages
across the
organisation
Leverages these
applications outside
the organisation
Common network
infrastructure such as
internet
BT Global Services
SOA Journey
Common standards
such as XML and
SOAP aid reuse
Flexibility to
orchestrate
composite
applications across
the enterprise
Phase 1 : Structural Integration
•
Developer led approach to using an integration platform - just make it work
•
Using inappropriate legacy integration patterns
•
Takes no heed of EAI, SOA or BEA best practice
CTMS
.event
topic
JMS Bridges
WLI NA
JMS
ORION MESSAGES
.service
topic
.domain.event
topic
JMS Bridges
.event
topic
CLASSIC
JMS
MESSAGES
WLI EU
.service
topic
Typical CTMS/ORION to Classic message flow:
EIS  topic  bridge to queue  BPM template  topic  bridge to topic  bridge to queue  BPM template  topic  EIS
Phase 2 : Process Integration
•
First serious attempt using BPM on WLI 8.1 - but...
•
Design did not decouple EIS’s : Billing design involved excessive custom development
•
Still message rather than service based
•
High costs showing up in the EIS domains
CLASSIC
ORDER
MGMT
WLS
Tuxedo
EJB/
java
RDBMS
GENEVA
BILLING
WLI
JMS
MESSAGES
CUSTOM XML
PL/SQL API
PROCESS
RDBMS
JCA
Adapter
EJB
MDB
ERROR
JMS
MESSAGES
GENEVA LOW
LEVEL PL/SQL
RDBMS
SOE Hub
Typical Classic to Geneva (fire and forget):
Clarify workflow  Tuxedo  WLS EJB interface layer  queue  BPM template  RDBMS JCA Adapter  Custom XML base PL/SQL interface 
Geneva PL/SQL  Geneva RDBMS
Errors:
Error returned from Custom or Geneva PL/SQL layers  BPM template  queue  WLS MDB  WLS EJB interface layer  Clarify RDBMS
Phase 3 : SOA
•
Loosely coupled EIS’s; canonical data format;
•
process orchestration; invokable re-usable services; consumer-provider paradigm
Hub Service
Process Definition
Message
Broker
Message
Broker
Message
Broker
8
Inbound Process
Definition
Outbound Process
Definition
5
Service Config
Service Config
Transformation/
Key Mapper
EDM
9
3
Transformation/
Key Mapper
4
Objectel
EDM
4a
EDM
8a
7
Objectel Reply
Document
6
Objectel Req.
Document
5a
Service Config
Transformation/
Key Mapper
Service Config
Transformation/
Key Mapper
9a
10
Clarify
EDM
Netcool
Netcool Req.
Document
Objectel
6a
Clarify Req.
Document
Clarify Reply
Document
7a
Clarify
11
1
Service Config
Transformation/
Key Mapper
2
Service Config
Service
Config
Key
Mapper
Transformation/
Key Mapper
12
Netcool Reply
Netcool
Document
Netcool
This scenario represents the alarm enrichment request
from Netcool
Hub Architecture Blueprint
Hub Components
Hub Services
Agenda
• Introducing BT Global Services
• Context & Business Challenges
• Integration Strategy
• SOA Design Evolution
• Evolving SOA Delivery
• Accomplishments
• Exploiting SOA
• The Next Level
• Conclusion
Evolving Delivery : Challenge
• A great architecture, but how to deliver it?
• Delivery mismatch : SOE followed traditional waterfall model
• Integration always last item on the agenda
• Issues with quality of release solution designs - boxes & lines
• Component teams tried to do P2P in secret to meet the schedule
: “malicious compliance”
Delivery Phase 1
• Drafted Greenfield delivery plan
• Aligned developers with the architecture
• Always delivered on time on / under budget
• Comms plan to drive buy-in across SOE
• Implemented SOA nomenclature - services, consumers,
providers. Squashed talk of ‘interfaces’
But
• Development squeeze, last to do LLD, first into test
• Data mapping crunch
• Expensive handshake between design / dev / test
Delivery Phase 2
• Re-aligned roles to support ‘multi-threading’ : one person per
service responsible for design, development, test,
documentation
• Planted designers into Solution Design area to drive
requirements capture and work package shaping
• De-coupled data mapping to enable parallel threads
But
• Dependencies on EIS providers meant delays
• Challenges queuing up behind waterfall quality gates
• Lengthy test cycles
Delivery Phase 3
• Re-shaped requirements to fit ‘services’ model
• De-coupled SOA from EIS deliveries - side by side approach
• Implemented Agile Development model
– ‘SWAT Teams’ tackle integration hotspots
– Involved the customer directly in small multi disciplinary team
• Combined bottom up with top down approach to service
definition (Matrix architecture)
• Aligned all SOA deliverables to business benefit & always
identify a GUI to demonstrate
Agenda
• Introducing BT Global Services
• Context & Business Challenges
• Integration Strategy
• SOA Design Evolution
• Evolving SOA Delivery
• Accomplishments
• Exploiting SOA
• The Next Level
• Conclusion
Results
• Moved from structural to 100% service based integration in 6
months
• Multiple re-usable services stored in service and infrastructure
component libraries
• Significant early reductions in cost of integration already
apparent within phase 1 (break even stage)
• Significant increase in delivery velocity
• BT using GS experience as part of full-scale roll out of SOA
Agenda
• Introducing BT Global Services
• Context & Business Challenges
• Integration Strategy
• SOA Design Evolution
• Evolving SOA Delivery
• Accomplishments
• Exploiting SOA
• Conclusion
SOA Layered Architecture
Custom Portal Applications
VBC
App 1
VBC
App 2
VBC
App 3
VBC
App 4
Enterprise Infrastructure Services
Shared Business Services
Portal Services
Messaging & Brokering Services
Shared Application Services
Enterprise Services
Enterprise Applications
Livelink (Content Mgt.)
Siebel (SFA)
Directory Services
Clarify (CRM)
Geneva (Billing) ...
Enterprise Data
Customers
Products
Employees
Partners
B2B Prototype Example
• Challenge:
Build a prototype that demonstrates ability to deliver telecom services
in Third Generation Outsourcing Model
• Portal-agnostic, standards-based, e-bonding solution to
empower north-, south-, east- and west-bound IT Service
Management across a multi-vendor, multi-asset, global
environment
Delivered in 4 weeks by re-using existing services and deploying via
web services gateway
Service Management Prototype : Architecture
Consumer
Customer OperationsConsumer
Portlet/s Portlet/s
(WSRP) (WSRP)
Portal/s
B2B
Gatewa
y
Partner Portal
OSS
BT Portal
Portlet Portlet
(WSRP)(WSRP)
Portlet Portlet
(WSRP)(WSRP)
Order
OSS
Quote Performa Custom
Invoic
er
Ticket Alarm Manag
nce
e
Report
er
Report
B2B
Gatew
ay
B2B
Gateway
Secure
Interconnect
EAI Platform
Order
Mngnt
Settleme
Product
Service Performa
nts &
Catalogu
Problem
nce
Billing
e&
Mngnt
Mngnt
Mngnt
Pricing
Enterprise Applications
Data
Warehous
e
Agenda
• Introducing BT Global Services
• Context & Business Challenges
• Integration Strategy
• SOA Design Evolution
• Evolving SOA Delivery
• Accomplishments
• Exploiting SOA
• The Next Level
• Conclusion
BT’s Matrix Architecture
Collaborative
Space
Customer & Commercial Management
Enterprise
Management
Customer & Channel Management
Selling
Professional
Services
Billing & Payments
Proposition Creation & Handling
ICT Contract Handling
Partners
& OLOs
Portal
Functions
BT People
Web
services
Management
Business-level Assurance
Service Execution
Service Management
Service Fulfillment
Network location
Service Support
Session control
Profiles
Presence
SLA Management
Messaging
Availability Management
Connectivity
resources
Media
Resources
Event Management
party apps
Outsourcing Management
Customers
and users
Authentication & Authorisation
Service Execution & Management
Trading
Gateways
3rd
Supplier
Management
Business
Intelligence
Knowledge
Management
&
Collaboration
Business
Support
Finance
ICT Infrastructure Management
Resource Planning
Resource fulfilment
Workforce
Management
Resource Assurance
Integration framework
21c network Capabilities
Utility Computing Capabilities
Applications & Content
BT PORTAL or GATEWAY
Manage
Customer
Contact
Manage
Customer
Manage
Billing
Account
Manage
Customer
Location
Manage
Customer
Order
Manage
Product
Instance
Manage
User
INFRASTRUCTURE
CRM PLATFORM
Manage
Order
Placement
Manage
Fulfilment
Order
Manage
Service
Fault
Manage
Service
Instance
Manage
Manual
Fallout
SERVICE MANAGEMENT PLATFORM
Manage
Network
Service
Implemtn.
Manage
Alarm
Correlation
Manage
User
Service
Profile
Manage
Network
Planning
Manage
Billing
Transactn
Manage
Invoice
Manage
Product
Instance
BILL PLATFORM
Manage
Network
Structure
Plan
Manage
Traffic
Forecasts.
CROSS DOMAIN PLATFORM
Manage
Network
Plan
Manage
Physical
Inventory
NEWORK ENGINEERING
Manage
SDH
Resource
Manage
PDH
Resource
Manage
ATM
Resource
Manage
MPLS
Resource
Manage
Job
Manage
Supplier
Order
Manage
Place
Manage
Appt.
SDH
PDH
ATM
MPLS
WM
B2B
NAD
???
Manage Supplier Order - Operations
List of Operations Offered
amendSupplierOrder
•
Amend will be used to modify Supplier Order, which hasn’t been passed the
PoNR (Point of No Return).
cancelSupplierOrder
•
Cancels (Aborts) the specified incomplete Supplier Order.
createSupplierOrder
•
Accepts and validates the Supplier Order information and sends Supplier
Order to the Supplier responsible for the delivery of the components and
manages the provision of deliverables.
publishEventsForSupplierOrde •
r
querySupplierOrder
•
receiveEventsForSupplierOrde•
r
This operation publishes Supplier Order related Infrastructure Events.
Returns the details of a specified Supplier Order.
This operation receives Infrastructure Events for the specified Supplier Order
or all Supplier Orders.
resumeSupplierOrder
•
Resumes the specified suspended Supplier Order by changing Order State
from Suspended to Running.
searchSupplierOrder
•
suspendSupplierOrder
•
Searches Supplier Orders, which either have or haven’t been fully
provisioned.
Suspends the specified incomplete Supplier Order by changing Order State
to Suspended.
updateSupplierOrder
•
This operation updates a Supplier Order.
Agenda
• Introducing BT Global Services
• Context & Business Challenges
• Integration Strategy
• SOA Design Evolution
• Evolving SOA Delivery
• Accomplishments
• Exploiting SOA
• The Next Level
• Conclusion
Learning Points
• Have a strategy that fits your business context
• Progressive rollout works effectively in large organisations - SOA
is a pebble in the pond
• Invest in getting the architecture right, then figure out how to
deliver it
• Delivery & execution are hard : prepare for war
• Have a good comms plan
• Don’t let architects champion integration - align to hard ROI
• The benefits of SOA are significant!!
Q&A
www.bt.com
Additional Slides
Our SOA Definition
•
Service-Oriented Architecture (SOA) is an architectural
paradigm in which loosely coupled, course grained application
components are distributed, combined and consumed over a
network as needed.
• The foundation of a SOA is a service layer that can be invoked
by applications, minimising the artificial dependencies within
systems of interacting software agents
• Key to SOA is the concept of a service, which is defined by
W3C as a unit of work completed by a service provider to
produce desired end results for a service consumer. The end
results are usually the change of state for the consumer but can
also be the change of state for the provider, or for both.
SOA Benefits
• Reduces systems/IT total cost of ownership
by up to one-third
• Maximises investments in existing systems by
integrating new applications and business processes
• Provides global enterprise visibility of information
and business processes
• Reduces the total cost of building, maintaining and
supporting application interfaces
SOA Layers
Connectivity
Inbound
Process
Service Config
Control
Transformation
Control
Key
Mapper
Brokering
Mechanism
Hub Service
Process
Receive
EIS Specific
Document
Request
Service Config
Receive EIS
document,
acquire
service
config and
transform to
EDM. Post
to Broker
(Message
or Process
Control).
Receive
Service Config
Invoke relevant
XQuery (dynamic)
Receive hub
common format
document
Translate to
EDM and
insert into
hub common
format
Request relevant EDM Keys from Key Mapper (dynamic)
Receive EDM Keys from Key Mapper
Post completed EDM document to Brokering mechanism (dynamic for synchronous calls)
Invoke Hub
Service Process
BIA Hub architecture
• A logical split within the hub
–
Hub Services implement the functional integration requirements of the BT GS business
domains
–
Hub Infrastructure (Components) implement the reusable foundations for the hub
• Design Guidelines in four areas
–
Process (including asynchronous and synchronous brokering)
–
Data (Key mapper and data transformation)
–
Connectivity (J2EE CA adapters, WLI controls, JMS or Web Services)
–
Non Functionals (performance, resilience, security, etc.)
• Based on WebLogic Platform 8.1
–
Capitalising on increased reusability and productivity features
Capability Detail
CAPABILITY
OPERATION
CAPABILITY
OPERATION
CAPABILITY
OPERATION
API API API
API API API
API API API
EXPOSURE LAYER
API
API
API
INTEGRATION LAYER
COTS / APPLICATION LAYER
A Matrix Capability Deployed
OSS
Matrix
Capabilities
LOB
Integration
LOB
Infrastructure
BT
Suppliers
D-TAG
SFJ
Neuf
Telecom
SOE
Classic
Manage
Supplier
Order
SOE EAI
Hub
BTW B2B
Gateway
Unisys
BBNed
Belgacom
A Service
Delivery
Application
etc
Increasing Technical Abstraction
SOE Integration
Release 3.0
• Total EAI Services
18
• Re-used EAI Services
0
• New EAI Interfaces
3
(Netcool; Expedio; Objectel)
• Re-used EAI Interfaces
4
(Classic; Geneva; CTMS; Orion)
Release 4.0
• Total EAI Services
20+
• Re-used EAI Services
10+
• New EAI System Interfaces
8+
• Re-used EAI System Interfaces 6+ ( “ )