OSS product vendors
•ADC (provisioning: wireline, cable)
•AI Metrics (order management, inventory and provisioning: wireline, next-gen, enterprise)
•Co-Manage (inventory, provisioning: data - ATM/FR/DSL/SONET/IP/IP-VPN) Cramer (provisioning, inventory, order management: mobile, voice, data)
•Eftia OSS Solutions (order management, provisioning, inventory: wireline, CLEC)
•Granite (provisioning and inventory: wireline, mobile, enterprise)
•Metasolv (order management, provisioning, inventory: wireline, wireless, data, isp)
•NetCracker (order management, provisioning, inventory: wireline, next-gen, data)
•Peregrine Systems (inventory management: wireline, next-gen)
•Sigma Systems (provisioning: cable)
•Telecordia: (order management, provisioning, inventory, dispatch: RBOC wireline)
•Visionael (inventory management: next-gen)
Others
•In-house developers
•ILEC/CLEC provisioning gateways (DSET, Nightfire, Quintessant, Wisor)
•Billing services vendors: Amdocs, Convergys, CSG, Infodirections
•Custom solutions (consultants/integrators)
•Legacy systems
Showing posts with label Order Management. Show all posts
Showing posts with label Order Management. Show all posts
Wednesday, 27 January 2010
Wednesday, 20 January 2010
Service Fulfillment Process : OSS
The "fulfillment" process embodies a range of OSSs — including
order management,
inventory,
provisioning,
service activation.
Order Management :
The order management and provisioning processes is the key OSSs involved in configuring the network to deliver the service desired by the customer (i.e., fulfillment).
The aim of an order management system (OMS) is to order the service the customer requests, support changes when necessary, keep the customer informed with meaningful progress of their order, and track and manage to successful and on-time completion.
The process begins with an order or, in some cases, pre-sale activity. The process ends with a completed order, a delighted customer and sufficient information to build or update a customer account record in trouble/problem handling, performance reporting and billing processes and systems.
Benifits of Order Management :
Time-to-market for new services is minimized
Failed orders is reduced to zero
Time to deliver services is minimized
Labor-intensive manual processes are eliminated
Reliable service to customers
Features of Order Management :
Accepting orders
Pre-order activity
Integration with Inventory database
Integration with SLA to know whether the customer is eligible for the service ordered and also to estimate the price for the service.
Reserve available facilities to support the order.
Initiate service installation
Notifying the customer
Initiate billing process
Order plan development
Request customer deposit
Issue order and tracking order status
Integration with workflow management system to dispatch a technician to install a service
Web ordering
Data-driven Architecture
API Support
Workflow engine
Notification for new ticket assignments or escalations to appropriate personnel, individuals or teams
Multi Platform Support
Quote service price
Payment engine
Integration with CRM
Core Business processes in Order Management:
Accepting orders
Pre-order activity and Credit Check
Price estimates
Order plan development
Request customer deposit
Reserve number
Initiate service installation
Notifying the customer
Initiate billing process
Order Manager:
The order manager coordinates all aspects and processes related to fulfilling an order — including validation, service decomposition, inventory update, provisioning, billing and testing
Provisioning Process:
The provisioning OSS works with the order manager to activate the service within the corresponding network element(s).The provisioning OSS also handles configuring the network for dynamically-oriented transactions — such as authentication, accounting, authorization, roaming, etc.
OMS Detailed Business Processes[Generic]:
(1) validate the order whether it is completed or not
(1 A)Determine which services create the product offering/Product Bundling
(1 B)Determine key configuration/design attributes for the service
(1 C)Steps required to configure the service.
(2)For each service , check whether inventory is available and assign.
(3)If additional infrastructure is required schedule the installation via the WFMS[Work Force Management System] or any partner.
(4)Schedule any internal configuration CPE installation etc.
(5)Provisioning Commands to the network subsystems or the network elements.
(6)Update Inventory [Logical and Physical]
(7)Perform Testing
(8)Start Billing
(9)Update customer management ,service assurance.
Service Fulfillment flow:
•Sales process caters for the customer queries, for the various available services.
•Customer places the service order directly to the order management system or through sales process.
•Order management process hands over this order to Service Configuration process to activate the service.Customer related details are saved in the OMS, which can be used by the assurance and billing processes.
•Service Configuration system assigns this service request to Network Provisioning System , that in turn sends this request to its sub-process “Network Configuration and Routing” to actually configure the service at Network Element Level.
•Network Configuration and Routing system checks the validity and availability of the network data through Network Inventory Management sub-process and then configures the service on Network Element Management and network elements .
•After configuration of Service, Security sub-process checks for the network access on the configured elements .
•Network Configuration and Routing sub-process requests the Test Management sub-process to check the configured service . This test sub-process checks whether configured service is working or not . Test completion results are sent back to the Network Configuration and Routing sub-process .
•Network Configuration and routing sub-process sends the network completion status to the Network Provisioning process . If the Service is successfully configured, Network Inventory Management sub-process is updated with data used for assigning the service.
•Network provisioning system updates the Service Configuration process after assignment of service is completed .
•Service Provisioning process informs the Order Management about the result of Service Request . It also updates billing system to start the billing for the given customer.
•Sales process or Order Management system informs the Customer about the activation of service it has asked for.
order management,
inventory,
provisioning,
service activation.
Order Management :
The order management and provisioning processes is the key OSSs involved in configuring the network to deliver the service desired by the customer (i.e., fulfillment).
The aim of an order management system (OMS) is to order the service the customer requests, support changes when necessary, keep the customer informed with meaningful progress of their order, and track and manage to successful and on-time completion.
The process begins with an order or, in some cases, pre-sale activity. The process ends with a completed order, a delighted customer and sufficient information to build or update a customer account record in trouble/problem handling, performance reporting and billing processes and systems.
Benifits of Order Management :
Time-to-market for new services is minimized
Failed orders is reduced to zero
Time to deliver services is minimized
Labor-intensive manual processes are eliminated
Reliable service to customers
Features of Order Management :
Accepting orders
Pre-order activity
Integration with Inventory database
Integration with SLA to know whether the customer is eligible for the service ordered and also to estimate the price for the service.
Reserve available facilities to support the order.
Initiate service installation
Notifying the customer
Initiate billing process
Order plan development
Request customer deposit
Issue order and tracking order status
Integration with workflow management system to dispatch a technician to install a service
Web ordering
Data-driven Architecture
API Support
Workflow engine
Notification for new ticket assignments or escalations to appropriate personnel, individuals or teams
Multi Platform Support
Quote service price
Payment engine
Integration with CRM
Core Business processes in Order Management:
Accepting orders
Pre-order activity and Credit Check
Price estimates
Order plan development
Request customer deposit
Reserve number
Initiate service installation
Notifying the customer
Initiate billing process
Order Manager:
The order manager coordinates all aspects and processes related to fulfilling an order — including validation, service decomposition, inventory update, provisioning, billing and testing
Provisioning Process:
The provisioning OSS works with the order manager to activate the service within the corresponding network element(s).The provisioning OSS also handles configuring the network for dynamically-oriented transactions — such as authentication, accounting, authorization, roaming, etc.
OMS Detailed Business Processes[Generic]:
(1) validate the order whether it is completed or not
(1 A)Determine which services create the product offering/Product Bundling
(1 B)Determine key configuration/design attributes for the service
(1 C)Steps required to configure the service.
(2)For each service , check whether inventory is available and assign.
(3)If additional infrastructure is required schedule the installation via the WFMS[Work Force Management System] or any partner.
(4)Schedule any internal configuration CPE installation etc.
(5)Provisioning Commands to the network subsystems or the network elements.
(6)Update Inventory [Logical and Physical]
(7)Perform Testing
(8)Start Billing
(9)Update customer management ,service assurance.
Service Fulfillment flow:
•Sales process caters for the customer queries, for the various available services.
•Customer places the service order directly to the order management system or through sales process.
•Order management process hands over this order to Service Configuration process to activate the service.Customer related details are saved in the OMS, which can be used by the assurance and billing processes.
•Service Configuration system assigns this service request to Network Provisioning System , that in turn sends this request to its sub-process “Network Configuration and Routing” to actually configure the service at Network Element Level.
•Network Configuration and Routing system checks the validity and availability of the network data through Network Inventory Management sub-process and then configures the service on Network Element Management and network elements .
•After configuration of Service, Security sub-process checks for the network access on the configured elements .
•Network Configuration and Routing sub-process requests the Test Management sub-process to check the configured service . This test sub-process checks whether configured service is working or not . Test completion results are sent back to the Network Configuration and Routing sub-process .
•Network Configuration and routing sub-process sends the network completion status to the Network Provisioning process . If the Service is successfully configured, Network Inventory Management sub-process is updated with data used for assigning the service.
•Network provisioning system updates the Service Configuration process after assignment of service is completed .
•Service Provisioning process informs the Order Management about the result of Service Request . It also updates billing system to start the billing for the given customer.
•Sales process or Order Management system informs the Customer about the activation of service it has asked for.
Tuesday, 19 January 2010
OSS BSS Challenges
Challenging IT problems
Requirements are a constantly moving target
Legacy heritage
Cost tradeoffs difficult to quantify and predict
Difficult to get it right the first time
Multiple generations software and infrastructure
Theory (getting it right) doesn't align with pragmatics (good enough)
Requirements are a constantly moving target
Legacy heritage
Cost tradeoffs difficult to quantify and predict
Difficult to get it right the first time
Multiple generations software and infrastructure
Theory (getting it right) doesn't align with pragmatics (good enough)
Role of Business Support System
Business support systems (BSS) are the components that a telephone operator or telco uses to run its business operations towards customer. BSS and OSS platforms are linked in the need to support various end to end services. Each area has its own data and service responsibilities.
Role of business support systems:
The role of business support systems in a service provider is to cover four main areas:
Product management
Customer management
Revenue management
Order management
Product management:
Product management supports product development, the sales and management of products, offers and bundles to businesses and mass-market customers. Product management regularly includes offering cross-product discounts, appropriate pricing and customer loyalty programmes.
Customer management:
Service providers require a single view of the customer and regularly need to support complex hierarchies across customer-facing applications (customer relationship management). Customer management also covers requirements for partner management and 24x7 web-based customer self-service. Customer management can also be thought of a full-fledge customer relationship management systems implemented to help customer care agents handle the customers in a better and informed manner.
Revenue management:
Revenue management is a BSS focus on billing, charging and settlement, that can handle any combination of OSS services, products and offers. BSS revenue management supports OSS order provisioning and often partner settlement.
Order management:
Order management as a beginning of assurance is normally associated with Operational Support Systems though Business Support Systems are often the business driver for fulfillment management and order provisioning.
Role of business support systems:
The role of business support systems in a service provider is to cover four main areas:
Product management
Customer management
Revenue management
Order management
Product management:
Product management supports product development, the sales and management of products, offers and bundles to businesses and mass-market customers. Product management regularly includes offering cross-product discounts, appropriate pricing and customer loyalty programmes.
Customer management:
Service providers require a single view of the customer and regularly need to support complex hierarchies across customer-facing applications (customer relationship management). Customer management also covers requirements for partner management and 24x7 web-based customer self-service. Customer management can also be thought of a full-fledge customer relationship management systems implemented to help customer care agents handle the customers in a better and informed manner.
Revenue management:
Revenue management is a BSS focus on billing, charging and settlement, that can handle any combination of OSS services, products and offers. BSS revenue management supports OSS order provisioning and often partner settlement.
Order management:
Order management as a beginning of assurance is normally associated with Operational Support Systems though Business Support Systems are often the business driver for fulfillment management and order provisioning.
Subscribe to:
Posts (Atom)