noe new order engine - red hat legacy order management at the end of lifecycle partial use of esb...

NOE – New Order Engine

Migrating a Tier-1 Teleco Order Management Engine to Red Hat JBoss Middleware

Jaroslav BlazekSenior Technology Architect, AccentureRadan BaseSolution Architect, Accenture

Agenda NOE Management Summary Architecture Highlight & Evolution Application Architecture Technical Architecture Summary & Drivers

Why NOE – Perfect Storm

Management Summary

Business Challenge / Approach

Client requested analyzes and implementation of New Order Engine replacing current WLI based Order Engine Open Source jBoss platforms were preselected for NOE implementation Analyzes was performed to validate platform selection and plan next stages NOE roadmap was prepared including PoC with infrastructure, functional and performance tests Production Pilot with Logistics processes Replacement of legacy OM platform for mobile / fixed services fullfilment Implementation of Order Capture & Validation tier replacing Siebel functionality. Thin External Ordering Application Completion of CRM Replacement. Thin CRM solution with BPM driven core based on selected portal framework

Execution Architecture

(simplified)

Dev. ArchitectureResults

NOE platform based on Open Source products (jBoss BRMS/SOA) PoC delivered in February 2013 NOE is configurable product driven order decomposition and fulfillment engine NOE is fully capable to process Siebel Orders towards OSS systems NOE is aligned with industry and technology standards (TAM, SID, BPMN2 ..) and E2E architecture is validated with RedHat Product roadmap outlined for full CRM replacement with Open Source based applications

ESB:SwitchYard 0.8

Application Server:Jboss 6.0

DB:Oracle 11g

jBoss Studio

BRMS v5.3SOA v6 (alfa)

Messaging:HornetQ 2.2.16 with GFS

HA

Client Context

Client is a Tier-1 convergent telco operator in Czech Republic providing fixed and mobile voice/data services for more than seven million subscribers.

This is a universal provider offering complex portfolio of services for residential and corporate clients.

Project Timeline

8/13/2012 3/8/2013

9/1/2012 10/1/2012 11/1/2012 12/1/2012 1/1/2013 2/1/2013 3/1/2013

8/13/2012 12/31/2014

10/1/2012 1/1/2013 4/1/2013 7/1/2013 10/1/2013 1/1/2014 4/1/2014 7/1/2014 10/1/2014

Aug - SepFS

Analyzes

Sep - Mar

Phase1- PoCMar - Jun

NMD

Jun - Sep

Minerva

Sep - Dec

Minerva Live / NOE Next Stages (FIX support, IBWLI, CIP-BPM..)

2013

R03

Oct

R04

12/27/2012 - 3/8/2013

Phase 1 - Proof of Concept

8/13/2012 - 12/27/2012

Feasibility Study - Analyses

Aggressive Timeline and fast concept 2 production Feasibility start August 2012 4 month for feasibility study (including infrastructure tests) 3 month for PoC (complete framework and selected scenarios test) 10 month from idea to production

Timeline Details

Production Deployment

Release 0 – Logistics processes for Mobile (June 2013)

Release 1 - Mobile ordering processes (September 2013)

Release 2 – Fixed ordering process (2014)

Release 3 – Order Capture and Validation

NOE Framework Evolution

Framework evolution was driven by BSS transformation program (CRM revitalization)

NOE Application is delivered by Communications Industry Node within our Technology Delivery Center in Central and Eastern Europe.

Architecture Highlights

Principles followed by the NOE Solution

Based on Open Source products Cost effective

Low vendor binding

Clean architecture Aligned with Client architecture axioms

Supporting EA alignment with TAM

Using industry standards / architecture patterns (BPMN2, SID ..)

Validated against common architecture principles

Targeting architecture concerns

Open architecture prepared for smooth extension towards front-end applications (OCV, eChannel, CRM)

Covering functional/non-functional requirements Functional enablers for Ordering processes and future OCV functionality

Performance scalability and resilience of the platform

Ongoing vendor validation Direct RedHat involvement - Partner Support

Architecture reviews

Innovation Award winning solution

CRM

WLI

Web Self Care

IVR

SMS Server

Mobile Billing

Fixed Billing

CIP

ESB

Legacy Applications

MobileNetwork

FixedNetwork

SPC

ODS

BL

CustomerOrderAsset

NOE Evolution (Starting Point)

Fragmented BSS and Integration domain

CRM centric architecture with Siebel

Legacy Order Management at the end of lifecycle

Partial use of ESB for extra domain communication

Customer ManagementOrder Capture & ValidationAsset InventoryOrder InventoryCFS Catalogue Master

Order Orchestration(Mobile/Fix)Non-ordering processes

Fixed Billing

CRM

WLI

Mobile Billing

CIP

ESB

Legacy Applications

MobileNetwork

FixedNetwork

SPC

ODS

NOE

Network Provisioning

Billing

Adapters

CustomerOrderAsset

Order

Web Self Care

IVR

SMS Server

SFANEOS

Legacy OM orchestration preserved for Fixed orders

Legacy Components

Changed Components

New Systems

NOE Evolution (Mobile Stage)

First full-production stage

Fully functional OM framework with Mobile proposition

Parallel run with legacy OM for Fixed orders

CRM centric model preserved with OCV in Siebel

Non-ordering support provided for Ordering GW services / other BPM processes

NOE used for Mobile orders orchestrationAnd related non-ordering proc.

Revitalized CRMSimplified ordering processes for Mobile (new proposition)

Adapters introduces for smooth integration with Network and billing systems

NOE Part:

New Order Engine Framework (data model, common APIs, common execution

components ..)

Mobile configuration and components (catalogue metadata, fulfillment workflows -

mobile application integration)

Support for Mobile ordering + fixed processes (Order GW, Recharging, VPN handling

..)

Rich monitoring and administration console

Other Components (part of program):

Siebel components – Mobile functionality (order capture & valicdation)

ESB components (APIs for NOE inbound/outbound)

Application adapters (NE / Billing / SAP / DMS / mODS ..)

Implementation Summary

Fixed Billing

CRM

Mobile Billing

CIP

ESB

Legacy Applications

MobileNetwork

FixedNetwork

ODS

NOE

Network Provisioning

Billing

Adapters

CustomerOrderAsset

Order

SFANEOS

Web Self Care

IVR

SMS Server

Order Orchestration(Mobile/Fix)Non-ordering processesOrder InventoryCFS SID Catalogue Slave

Customer ManagementOrder Capture & ValidationAsset InventoryOrder InventoryCommercial Catalogue Master

New Self Care platformPre-integrated to CRM and COM

Legacy Components

Changed Components

New Systems

NOE Evolution (Convergent Stage - Next)

Second production stage with fixed/mobile convergent ordering support

Decommission of legacy OM components

Full decommissioning of legacy OM platform

Introduction of New Self Care platform (simple e.g. eShop)

CRMWeb Self

Care

IVR

SMS Server

Consolidated Billing

ESB

Legacy Applications

MobileNetwork

FixedNetwork

NOENetwork

Provisioning

Billing

Adapters

CustomerOrderAsset

SFA

ERP

RTDCAR

RTD

ConsolidatedDWH

Big Data

Customer ManagementShared Portal Platform

Order Capture & ValidationOrder Orchestration (Mobile/Fix)Non-ordering processesOrder InventoryAsset InventoryCFS SID Catalogue Master

Exposed OCV ServicesExposed Customer ServicesShared Catalogue and Rules

Cloud Based SFA

New ERP System

New BI ComponentsConsolidated DWHReal Time Decisioning

Self Care platformFully functional eCare with shared Ordering core

Consolidated Billing

Legacy Components

Changed Components

New Systems

NOE Evolution (Future Target -SHEM) Future target with light channel

applications and full implementation of OM with OCV (Order Capture & Validation)

Thin CRM application integrated with shared process driven ordering core

Web Self Care sharing CRM components

Integration with Real Time Decisioning for NBA/NBO

Core Part:

Extension for Order Capture and Validation – OCV (process driven application using interactive BPM processes)

Customer Management process support and inventories on mid layer

Extension of service platform for channel applications integration

Other Components:

Implementation of thin CRM application based on Portal technology with NOE backend

Implementation of shared OCV front end application with NOE backend

Implementation of eCare modules

Other application components implementation

Consolidated DWH

Real Time Decisioning supporting NBA/NBO with seamless integration to OCV

Consolidated/convergent Billing system

Replacement of core ESB

Future Target - SHEM

SMART Handling and Execution Management

Metadata

Repositories

(Product Rules

& Process Cat.)

Order & Plan

Repository

Process

Governance

Presentation Order Management ISB(EAI &

Orchestration)

Resources

RDBMS

Legacy

Applications

OCC Service

Layer

Decomposition Plan Execution Process

Execution

CIP ESB (Oracle ALSB)

Apache

Tomcat

Jboss jBPM

Jboss Business Rules

(Drools)

Drools

Repository

Hibernate

Custom Components

JBoss Application Server

(EJB3, RHC, GFS, HornetQ Messaging)

Jboss BRMS

(UI Support)

SwitchYard

16

NOE Process Structure & Technical Components

NOE is utilizing BRMS and SOA RH Platforms• Maximal reuse of OOTB functionality• Accent on HA and scalability

Order & Plan

Repository

Process Governance

Order

Management

Collision Detection

Decomposition

Process Execution

Plan Execution

ESB

NOE Application Architecture - Reusability

Inbound

Requests Processing / Load

Control and Process Routing

Non-Ordering requests processing

Workflow & External Callouts

Ordering requests processing

Order Decomposition & Execution

Reusable ComponentsFull reuse (configuration only)

Partial modification

New components

Reusability & Availability

Solution available as standalone Asset or part of other Accenture offerings (Leopard BSS)

Kick-start package available (virtual machine with ready to start pre-configured product)

Second European Tier-1 telco in progress of adopting same solution (go-live Sept. 2014)

Further evolution of Asset driven by running projects in-progress

Additional functionality (OCV, NBA..)

Porting on new platform versions (BRMS/FUSE)

Extending Open Source stack (e.g. replacing Oracle with PostgreSQL)

NOE Plan Development

NOE is processing Siebel Orders in CDM format

Order is decomposed into tasks Tasks grouped (affinity) Execution plan created and

consolidated

NOE Plan Execution

Execution module is processing Ex. Plans In each cycle plan is evaluated and tasks to be

executed identified Fulfillment workflows with external callouts are

modeled in jBPM

21

NOE CDM DefinitionSID Based

SW Element Usage

Custom JAVA Components

EJB

Hibernate entity objects

POJOs and custom JAVA services

BPMN 2.0 Workflows (jBPM)

Governance

Fulfillment

DROOLs rules (plain rules / generated

from template)

Process routing

In-process decision rules

Ordering (decomposition / plan creation /

consolidation)

Plan execution

Data Transformations

SwitchYard Web Services (Exposed on

light weight Internal Service Bus)

NOE Technical Architecture

Architecture based on Intel RHEL OS HW Balancing for WebServices JMS based balancing for

application core

CPU: 16 coresMemory: 32 GB

server1

Process Execution- Governance Workflows

- Fulfillment Workflows

balancer

Application Min. Requirement – 14 cores/30GB

Plan Execution

Decomposition

HornetQ

(Primary)

GFS2


server2




Plan Execution

Decomposition

HornetQ

(Backup)

GFS2


server3




Plan Execution

Decomposition

UI Applications-GUVNOR

-Business Central

-Monitoring Consoles

BAM


server4




Plan Execution

Decomposition


-Business Central


BAM

RHC for GFS

CPU: 4 cores – stage 1 (8 cores stage 2)Memory: 32 GB

Inventory DB

Logging DB

Inventory DB

Logging DB

Failover Cluster

RHEL 6.2+EAP 6BRMS 5.3




Oracle 11gOracle 11g


JMSFailover

Loadbalancingon JMS

Loadbalancingon JMS

HW Loadbalanced


server1



balancer


Plan Execution

Decomposition

HornetQ

(Primary)

GFS2


server2




Plan Execution

Decomposition

HornetQ

(Backup)

GFS2


server3




Plan Execution

Decomposition


-Business Central


BAM


server4




Plan Execution

Decomposition


-Business Central


BAM

RHC for GFS


Inventory DB

Logging DB

Inventory DB

Logging DB

Failover Cluster

RHEL 6.2+EAP 6BRMS 5.3RHEL 6.2+

EAP 6BRMS 5.3



Oracle 11gOracle 11g


Failove (active/standby)

Client’s Business Case – Drivers

Business & Operations

Legacy OM platform (Oracle WebLogic) not supported by

Vendor (EOL)

Risk of long term outage with significant impact on

Business operations

BSS Transformation program running - right time for

change

Decrease CAPEX/OPEX costs

Dependency on Oracle vendor – wide Oracle SW portfolio

used

Legacy platform with limited monitoring and administration

capabilities

Missing Load Control and Process Governance

functionalities

Technology & EA

TAM model compliance

Alignment with architecture axioms / Industry standards

Distributed Order Management Functionality

Missing central product catalogue and/or synchronization

with domain catalogues

Complicated channel integration (OCV / Siebel Ordering

Gateways ..)

Client’s Business Case – BC comparison

Customer compared two possibilities

Replace current HW platform with Oracle ExaLogic and upgrade/reimplementation application to new Weblogic version

Develop Framework on Red Hat JBoss SW and replace current application

Framework Development on RH JBosswas chosen because of

Total OPEX and CAPEX savings are down by 38% in 5years

License savings are cca 49%

Platform HW and SW costs (OS/HA..) needs are lower by 30%

Customer looking for experience with Open Source products, and possible further evolvement within EA

Risk analysis and assessment were acceptable for IT Top Management – Feasibility study and Proof of Concept (with future significant Framework reuse) was planned and achieved

Gartner recommendation to use RH platforms in client context

Overall Roadmap Target Benefits Application portfolio consolidated on Open Source Platform

Low TCO for E2E solution

Cost effective scalable platform with low vendor binding (commodity development on JAVA)

Shared catalogue and process definition repositories – single point of true for all channel applications

Fast time to marked allowed by easy configuration of Offerings in commercial catalogue with direct mapping on

Customer Facing Services

Effective cross-sell/up-sell supported by Real Time Decisioning for next best action support (NBA/NBO)

Extendable architecture based on open standards using rich Open Source platforms (Jboss BRMS/SOA)

Easy integration of additional internal or external channel applications (e.g. NVNO)

Encapsulation and Isolation for core functional components allowing effective reuse.

Way to Success Clear architecture Vision

Strong architecture governance

Tight cooperation with Vendor support teams (partner / technical / sales)

Accent on native RedHat platform capabilities (Out of the box thinking)

Open source evangelization / Client awareness

…Q&AThank you for attention

RedHat Alliance, Sales and Partner Support team: Stefano Passiglia Krzysztof ( Chris ) Rocki Karoly Nagy Jeff Bride Jeff DeLong

Score us on mobile app ..

Presentation available on www.redhat.com/summit/2014/presentations

http://www.redhat.com/summit/2014/presentations

Backup Slides

noe new order engine - red hat legacy order management at the end of lifecycle partial use of esb...

Documents