1 BUSINESS SUMMARY

Tender Details: Respond to the tender by 5pm EST, April 3, 2013 to leo.manhanga@coriolisys.com. For any questions regarding the tender email to joey.muronda@coriolisys.com

1.1 Scope & Objectives

We are seeking a company that will provide an Oracle ERP platform that support the daily operation of a business. The platform should incorporate the following Oracle ERP Systems

Oracle Business and Revenue Management System(BRM) Includes fraud management system module Oracle CRM system (Siebel) Oracle Integration Platform(AIA) or SOA Oracle Telecom Retail POS

Objective and Scope

The objective of this project is that the customer gets a unified view of the account information, single bill for the services offered, single payment mechanism for all the services which results in a single product and price catalogue for all the pre-paid as well as post-paid customer base. This will help better time to market the products and reduced cost of implementation.

1.2 Cost

Please indicate expected onsite requirement and offsite requirement and the respective costs. The project is located outside India. Provide the cost, hours, labour in more like the fashion below how many hours per each application are needed to complete the work. This is for Oracle CRM, Oracle BRM, Oracle AIA/SOA and Oracle POS. We also going to accept a Fixed bid, but with a breakdown in a more or less approach below;

Roles Hourly Rate - USD (Onsite)

Hourly Rate - USD (Offshore) No# of FTE

(Onsite) No# of FTE (Offshore)

Estimated Man hours

Integration Architect Sr Developers Developers Project Manager Testers Administrator

2 SCOPE DETAILS

2.1 Understanding of Functional Scope

Following are in scope

Business Analysis, Architecture and design the systems BSS Systems Integrations

Tender for Oracle ERP Business Support System (BSS)

2 of 5

Data migration and Upgrade activities

Customizations/implementations of OSS/BSS business requirements

Performance fine tuning

Production and solution support service including training end users

Out-of-Scope

Following activities are considered as out of scope

Help desk support for applications.

Network Support.

Customization of third party/external interface API’s

Post production support (except warranty period support)

The Functional scope is depicted in the diagram below

2.2 Understanding of Technical Scope

The architectural design principles for COM topologies based on Oracle’s enterprise applications and middleware (e.g., Oracle BRM, Siebel CRM, Oracle Communications Order and Service Management, Oracle Product Hub for Communications and Oracle AIA for Communications). The architecture should provide the following advantages:

Ability to decouple commercial products from fulfilment flows for faster time to market Ability to decouple fulfilment topology from fulfilment flows for greater IT flexibility At offer design time, integration with Siebel to synchronize product class definitions to

minimize order fallout At order capture time, support for advanced customer order qualification

Tender for Oracle ERP Business Support System (BSS)

3 of 5

The diagram below provides shows how the Oracle CRM, Oracle BRM, Oracle AIA, Oracle POS, Oracle BIP, all fit together with the Network topology to provide a business support system we are looking to implement.

2.3 Understanding of Business requirements

3.1 Scope of Work

The Contractor will be providing development of Business support systems that include:

Oracle Business and Revenue Management System(BRM) Includes fraud management system module Oracle CRM system (Siebel) Oracle Integration Platform(AIA) or SOA Oracle Telecom Retail POS

3.1.1 In-Scope Activities

As defined in the scope, the company will carry out the following activities:

1. Business support system development:

Business Analysis, Architecture and design the systems BSS systems integrations

Tender for Oracle ERP Business Support System (BSS)

4 of 5

Data migration and Upgrade activities Customizations/implementations of OSS/BSS business requirements Performance fine tuning

2. System maintenance and Support: Our support activities will include:

Finding solutions to advanced problems raised by users Resolution of bug fixes Conduct SIT and support UAT testing for bug fixes

Updating knowledge repository with known problems and verified solutions for future reference

Perform root cause analysis, find patterns and help in preventive maintenance Assisting in review project rollout

3. Perform end user training as needed

3.2 Detailed Functional Components

3.2.1.1 Customer Relationship Management Component (Siebel)

It handles the following business scenarios:

Account Management Management of accounts through multilevel account hierarchies

based on complex account relationships Independent management of service accounts and billing accounts Management of account and customer information through profiles

Billing Management Integration with back-office billing systems Query and display of billing information Management of payment information, payment plans, bill adjustments, and bill profiles

Credit management Management of credit alerts Notification of customers who are delinquent in payment

Call center Optimization Single desktop for managing different types of customer interaction Integrated Web and IVR self-service functionality

Audit Trail Creation of a history of all the changes that have been made to various kinds of information

Records show who has accessed an item, what operation has been performed, when it was performed, and how the value was changed

Useful for maintaining security, examining the history of a particular record, and documenting modifications for future analysis and recordkeeping

Order configuration and management

Pricing management Trouble ticket and service request management

Usage, billing, and service detail

Tender for Oracle ERP Business Support System (BSS)

5 of 5

3.2.1.2 Integration Component (AIA) or Oracle SOA

AIA or SOA will provide the integration platform of the proposed applications to be implemented.

Oracle Process Integration Packs (PIPs) used in the Solution:

Order to Bill Product Life Cycle Management Order Management Customer Care Management

Agent Assisted Billing

a) Account Balance integration flow b) The Invoice integration flow c) The Service Usage integration flow d) The Payment integration flow e) The Adjustment integration flow

3.2.1.3 Retail Billing Component (BRM)

Oracle BRM will provide the Billing and Revenue management and should provide support in dealing with the Fraud Management System.

3.2.1.4 Fraud Management system (FMS)

Viewing Fraud alerts in Siebel Communications (End Users) Following Up with the Customer about a Fraud Alert (End User) Changing Fraud Thresholds in Siebel Communications (End User) Updating the Fraud Alert in Siebel Communications (End User) Additional End-User Tasks for Fraud Management in Siebel Communications

3.2.1.5 Retail POS (Point-of-Service)

We proposed an Oracle retail POS system. There is an option to build an internal application that supports a POS.

3.2.1.6 Mediation

Siloed legacy billing, rating and charging systems are expensive to maintain, lack interoperability, and cannot easily migrate to support next-generation services – factors that escalate CAPEX and OPEX. A unified mediation system with a flexible engine such as the Oracle Communications Online Mediation Controller resolves these issues for billing and charging systems, while enhancing revenue continuity and supporting next-generation network connectivity.