OSM Overview

Tech Mahindra Limited confidential© Tech Mahindra Limited 2008

Order & Service Management (OSM)

Product By ORACLEOracle Communications Provisioning

CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited

Course Objectives• Provisioning the orders• Getting a clear idea , how OSM is interacting with other

systems• Importing and exporting (portability) • Creating external orders using web services and xml api


Key points• Oracle bought the product from Metasolv

• OSM is the renamed term of P6 (Provisioning 6)

• Most recommended tool in Telecom domain which sits

in OSS layer of the telecom architecture and interact with other peer systems .

OSMProvisioningInventory Activation

OSS

Upper stream systems


OrderA contract made between a customer and a supplier for the supply of a range of

services in a determined quantity and quality, at an agreed price, and for delivery at or by a specified time .

• New connection• Suspend connection• Resume connection• Upgrade bandwidth• Downgrade bandwidth ….etc

An order consists of Process . A process is a sequence of tasks that are executed

consecutively to fulfill an order.


Order flow

Get network details from inventory

Send data to Activation

Update inventory Perform Line test

Trigger BillingUpgrade Bandwidth

TasksProcess

Order captured finishEnters OSMOrder created

A bank customer requests to increase his line bandwidth from 30 kbps to 50 kbps

Workflow


Basic Flow of an order :• Create order : The order enters the system through order entry interface and is initiated with

the state open.not_running.not_started.

• Submit order : The creation task completes and the workflow begins. The order transitions to the state open.running.in_progress.

• Complete tasks : Complete any number of tasks in the workflow. The order remains in the state open.running.in_progress.

• Complete last task : Complete the last task in the workflow. The order transitions to the state closed.completed.

• Delete order : The order is removed from the system.


Order states order progress in a lifecycle

An order’s progress can be tracked by its state at various stages of its life cycle. As tasks complete, the system updates the order state to recognize milestone achievements in the provisioning of the order. order states:• Not Started

• In Progress

• Suspended

• Cancelled

• Amending

• Canceling

• Completed


Order Decomp Fulfill

• Query/reserve network inventory

• Assign/design specific paths/ports based on availability & requirements

• Coordinate all tasks & systems required to deliver services

• Initiate activation/billing

Decompose Fulfill

Order Management DefinedFront Office / Back Office OM Functions

Back OfficeBack Office

Front OfficeFront OfficeEnd-to-end OM Lifecycle

Order CapturePreorder

TransactEngage• Needs Analysis• Guided selling• Customer profile

and account creation

• Address validation• Service eligibility

check • Credit check

• Service selection and configuration

• Order entry and validation

• Pricing• Move, Add, Change,

Disconnect (MACD)

• Partition bundled service orders into actual units of work

• Provide bi-direction updates of decomposed orders with CRM throughout the order lifecycle

Provisioning Control


Functional Architecture


What is OSM ?

Generally , OSM can be broadly seen as :

• Provisioning Product•Provisioning orchestration Product

OR

Service/Order Fulfillment Product= Provisioning + Orchestration


OSM as Provisioning Product

Provisioning means “providing” or “making something available”

According to Technical Group :

Provisioning is the automation of all steps required to create and manage ( setup, amend or revoke ) user or system access entitlements or data relative to electronically published services.

For example :

Telecom Provisioning means providing service to a user including everything necessary to setup the service such as equipment , wiring and transmission.


OSM as Orchestration Product

Execute the right tasks with the right data to the right systems and people at the right time

OrderingOrdering

InventoryInventory

Service Service ActivationActivation


Summary of overview

OSM manages the life cycle associated with the fulfillment of a customer's service order. This includes managing information from peer Operation Support System (OSS) applications required for provisioning, as well as managing the tasks to other OSS applications to complete the service order. OSM interfaces with each of these systems.


OSM Required Tools / Components

Component UseWeb Client Primary end-user toolAdministrator Design-time toolXML Model / HTML Report Design-time toolReporting Interface Module Admin, End-user toolWLS Console Primary deploy-time and

application monitoring toolCartridge Management Tool Assemble/deploy OSM models &

pluginsDatabase Utilities Data Manager for data transfers

Oracle Scripter for schema installOSM Installer Install OSMBEA WebLogic Server J2EE containerOracle RDBMS Data store


Tools / Components

OSM Server

BEA WebLogic Server(Application Server, J2EE Services, LDAP)

OSM Database (Oracle) CorporateLDAP

OSM Admin

Console

HTTP

OSMClient

Custom XMLApplication

Automation Framework

Plugin Plugin Plugin Plugin

JMS Message Bus

For an order to be created by OSM client , the workflow has to be configured in OSM Admin .

The OSM server is the main server which is deployed in the form of oms.ear in application server Bea Weblogic .

The data model used is Oracle

An order can be progressed either manually or automated using custom XML applications(XSLT) of java plugins .

OSM Admin and Weblogic are installed either on one machine or differently and theseare acessed by OSM client through Http calls across the network


OSM AdministratorOSM Administrator provides the interface to configure and manage the OSM

system. We use the OSM Administrator to construct the process definitions, order data requirements, workgroups, and associations that OSM requires

Design-time tool• Cartridge• Tasks• Processes• Views• Workgroup• Notifications• Process Exceptions


OSM Administrator : Cartridge

• A cartridge contains a full OSM metadata model as well as other components such as plug-ins , tasks ,assignment algorithms .

• Its in the form of XML which can be easily imported and exported

Cartridge

Process

Views

Data elements

State policiesTasks

Associations

Plugins Assignment algorithms

Grouping

Orders


Process: A workflow consisting of Tasks

Task CTask CProcess C

Task A

And

Task B

Task D

Start

Task E

Stop

Task C

?

Or

Task F

SPnTask A

And

Task B

Task D

Start

Task E

Stop

Task C

?

Or

Task F

Get network details from inventory

Send data to Activation

Update inventory Perform Line test

Trigger BillingUpgrade Bandwidth Tasks

ProcessOrder captured finish

Enters OSM

Order created


ViewsA view is a browser page that requires specific information which a task need to fulfill to progress the order

It is just like to display and provide data on screen to OSM .


WorkgroupsGroups who actually work for the task. There can be :• Manual workgroup• Inventory workgroup• …….. N workgroup

Each task is assigned a workgroup and their people are responsible for completion of a particular task


Process Exceptions

Process exception could be used to stop the order completely or redirect the order to another process

Restriction can be placed on process exception so that it can only be raised in certain tasks and by certain workgroup

An exception is an event, which occurs during the execution of a process, that disrupts the normal flow.


You can define Notification on certain conditions

Notifications can be classified as –

• Polled – Provisioning will repeatedly check for notification conditions at predefined intervals• Transitional – Notification is triggered when order goes into specific process, in specific task and in specific state

Notifications are messages sent by OSM to inform users of an event such as the receipt of a task or some state change etc…..

Notifications


OSM Client : For end-usersThe OSM Web Client provides the user interface to the worklist order tracking and operational reporting information. It lets you create, view, edit, track, and report on service orders in the OSM system using a web browser.

It consists of following views :

•Create Order•Work list•Order Editor•Order History•System reports•Query


Create order

Customer service orders can originate internally through OSM.


Order Editor For an order to progress required data elements has to be

added . Elements are displayed according to a order’s view at a given task.


Work listYou use the Work list to manage your tasks. It displays a list of orders currently located at the task or tasks for which you are responsible.


Order HistoryOrder History provides a process history for a given order. When task state changes occur, OSM records the date and time of the change, and the user who made the change


System Reports

Generates reports for pending , completed orders , completed tasks


Query

ref1

You can locate any order in the OSM system using the Query option. You can query for any order, including completed orders.


Thank you……

Documents

OSM Overview