SLT Mobitel

RFP - Oracle Advanced

Collection
Technical Request for proposal - Nov 2021
Contents

1 Introduction 1
1.1 The Background 1

2 Overall Description 1
2.1 Product Scope 1
2.2 Format of the Technical proposal 1
2.3 Scope of work 2
2.4 Approach and Methodology 3
2.4.1 Overall Project Plan 3
2.4.2 Timeframes, milestones and deliverables 4
2.4.3 Project Management 4
2.5 Training 4
2.5.1 Training Methodology 4
2.6 Post Production Support 5
2.7 Resumes of Personnel 5
2.7.1 Project Team of the vendor side 5
2.8 Customer Testimonials 7
2.9 Company Profile 7
2.10 Functional Requirement Specification 8
2.10.1 Response to FRS 8

3 . B – Functional Requirement Specification 9

3.1 Functional Requirement Specification 9

i
1 INTRODUCTION

Sri Lanka Telecom Mobitel (Pvt) Ltd (hereinafter referred to as “SLT Mobitel”) intends to implement the
Oracle Advanced Collection module (hereinafter referred to as “system”) with EBS R12 version to
improve and automate their debtor handling processes and operations. The purpose of this document is
to inform potential vendors the detailed information required (in the form of a proposal) to enable SLT
Mobitel to select a preferred supplier who will fulfil the needs of the implementation.

1.1 The Background

SLT Mobitel implemented Oracle EBS R12 version (12.3.4) in year 2016 with modules such as Order Mgt,
Inventory, Procurement, AP, AR, GL, CM, Treasury, EAM etc. Currently the system is used by more than
1000 users to carry out their day today business operations across all implemented modules.

However, the advanced collection activities are conducted in as a manual process. The purpose of this
project is to fully implement all functionalities of oracle Advanced Collection module in order to fulfil
collection needs of SLT Mobitel.

2 OVERALL DESCRIPTION

2.1 Product Scope

The scope of the implementation should include the complete set of functional and non-functional
requirements included in this document.

The high-level implementation scope included below.

1. Implementation of Oracle Advanced Collection module (R12)

2. Perform required Configurations, personalizations, Customizations, Workflows, and development of
customized reports.
3. Post production support

2.2 Format of the Technical

proposal

The format for submission of technical offer is as follows:

1. Index
2. Executive summary
3. Approach and Methodology
4. Training
5. Post Production Support
1
 6. Resumes of Personnel
7. Terms and Conditions
8. Customer Testimonials
9. Company Profile
10. Functional Requirement Specifications
11. Any other information as requested

2.3 Scope of work

Sr. No Task Illustrative list of activities/ deliverables

1. Functional  Appendix 3.B – Functional Requirement Specification.
solution

2. Implementation  Provide an action plan for implementation of the proposed solution

planning  The implementation plan should include the methodology to be followed,
product customization, site preparation for implementation, training
workshops to be conducted, details on training material, project
organization for implementation, responsibility matrix for the client and
vendor, test procedures, user acceptance test procedures etc.
 Implementation Plan should consist of the following features:
 Start and End date for each task
 Duration for each task in working days
 Man-days required for each task
 Resources allocated for each task
 Responsible party and resource
 A sign-off task to identify an end of a stage or a deliverable
 Appointment of required teams and steering committee along with
 Team responsibility
 Proposed members for those teams and their
responsibilities within that team
 Frequency of those team meetings
 Establish an escalation path for problem resolution
 Risk plan and assessment

3. Finalize new  Vendor may carryout following activities in order to establish new
Business business processes to implement the proposed application:
Processes in  Study of the existing processes.
Proposed

2
 application  Finalize the new business processes for SLT Mobitel
 Get sign-off for new business processes.
 vendor would provide an assessment document and new detailed
Business Processes shall be finalized after this phase.

4. Implementation  In accordance with the implementation plan that has been provided,
the vendor would deploy the system.
 The vendor would be responsible for Configurations, personalizations,
Customizations, workflow building and customized report
developments, performing test runs, training of users, obtaining user
acceptance.
 SLT Mobitel will provide the user acceptance signoff.
 Periodic status updates on an agreed upon basis.
 During and at the end of the implementation the vendor is expected to
provide:
User Guides, administration manuals, Training material,
Documented Migration Plans, Functional specs and technical
documents

5. Training  Vendor is expected to transfer knowledge to the ERP team of SLT

Mobitel to provide 1st level support
 Vendor is expected to transfer knowledge of the implementation to
internal ERP technical and functional teams.
 Vendor is expected to provide training for end users.

6. Post production  One months of PPS for L2 support for related functionalities.
support
 Vendor is also expected to work with Oracle global support and
resolve issues, SLT Mobitel will provide a CSI#

2.4 Approach and Methodology

2.4.1 Overall Project Plan

Vendor needed to provide a project plan starting from project initiation to post production
support.
The project plan should include the following:
 Clear separation of major activities
 Each major activity should identify all related sub-activities
 Milestones of each phase (Signoffs)
 Time allocation for each activity along with the duration and man-days.
3
  Resource allocation for each activity clearly identifying the responsible party and the team
member for that activity.

2.4.2 Timeframes, milestones and deliverables

The Vendor should provide the time frame of the project with key milestones and deliverables.

Vendor is expected to provide information as per below format.

.
Table A 1
Seq. phases of Milestones Deliverables Time Frame
No implementation
plan
1
2
3
4
5
6
7

2.4.3 Project Management

Vendor should provide the project management approach along with the methodology to
obtain user and management commitment to the project along with signoffs.
Further a clear project organization structure including vendor, SLT Mobitel roles and
responsibilities should be provided including an escalation path for resolution of problems.
The frequency of status meetings also to be mentioned.

2.5 Training

2.5.1 Training Methodology

Vendor should provide necessary training to End users to carry out the work using the
implemented module and ERP support team to provide first level support after go live.

SLT Mobitel expects the vendor to conduct multiple training programs to fulfil the training
requirements.

Further Vendor is expected to transfer knowledge of the implementation to internal ERP

technical and functional team.

Table A 2

4
 Serial Description Vendor Confirmation
Number (Yes/No)
1. The vendor should provide adequate training to end users to carry
out operations
2. The vendor should provide adequate training for support team to
provide first level support
3. The vendor should provide customized user guides and training
materials to SLT Mobitel
4 The Vendor should provide a knowledge transfer to the SLT
Mobitel support team on system configurations relevant for the
implemented workflows/ customizations/ personalization’s
reports etc.

2.6 Post Production Support

Two months of PPS for L2 support for related functionalities.

Vendor is also expected to work with Oracle global support and resolve issues SLT Mobitel will provide a CSI#

Vendor should provide responses according to below table.

Table A 3

Serial No Service/ Support Provided Vendor Confirmation

(Yes/No)
1.1. One month of PPS for L2 support for related functionalities
1.2. Vendor is also expected to work with Oracle global support and
resolve issues, SLT Mobitel will provide a CSI#

1.3. Vendor to provide a Man day rate to any support jobs related to
product which is not covered under 1.1 and 1.2 in Table A 3 –
Man day rate to be provided in the commercial proposal

2.7 Resumes of Personnel

2.7.1 Project Team of the vendor side

Vendor should clearly mention the teams who will be deployed in the implementation process.
Their main activities and responsibilities should be clearly inserted in the below table.

Table A 4

# Team/ Position Responsibilities Tasks Time

Team assigned Allocation
member
Name

5
 1 Team 1

1.1 Member 1

1.2 Member 2

1.3 Member 3

2 Team 2

 Vendor is expected to provide qualifications, past experiences of project members as per below formats

 It is compulsory that the same committed project team to be deployed from contract signing to closure of
the implementation if the Vendor has been selected.

Following templates to be filled for each resource proposed

Table A 5
Proposed Position:

Tasked involved (task identified

in the project plan)

Name of the resource

No of Years of EBS Years with the Current Firm

experience

Date of Birth:

Following table should be filled for each proposed resource with previous work experienced prior joining to
current firm
Table A 6
No Company Name Position held Period Responsibilities Remarks
undertook /
activities performed

Following table should be filled for all proposed members with relevant similar project experience.

6
 Table A 7
No Project Company Period Responsibilities Remarks
Description Assignment details undertook /
activities performed

Academic and Professional Qualification to be filled in below format for each and every proposed resource.
Table A 8
No. Qualification Institute Period

2.8 Customer Testimonials

Vendor should provide customer testimonials with projects completed on relevant implementation
scope in the below format shown below.
Table A 9
# Name of List of Relevant Industr No. Years of Nature of Service Implementation Contact
Client Products and y relationship Provided (e.g. Duration (with person’s
and Modules with the client implementation, start and end Details
Country Implemented training, support, dates)
etc.)

2.9 Company Profile

Vendor is expected to provide below information related to company profile

Table A 10

7
 No Details of the Implementation Partner Vendor Response

Registered company name of the implementer

Business registration number of the implementer
Date of company establishment
Address of the implementer
Name of the primary contact person
Number of years in operation with the above registered
name
Business Summary
Number of employees
No. of customers as of date

2.10 Functional Requirement

Specification

2.10.1 Response to FRS

Vendor must provide one of the following responses and may elaborate through comments how
the solution meets each of the functional requirements listed in below 3.B

 F – System is fully compliant and does not require any modifications to fulfil the
requirement.
 M – With a minor modification, it may be possible to meet the requirement.
 C - With a considerable modification (or by customisation) it may be possible to meet the
requirement.
 N - System does not support the requirement at all.

Vendor should provide the responses in above format and any other responses may consider as
Not Supported (N)
Except for the requirements marked as “N”, all other requirements would be considered as being
provided by the vendor within the cost stated through the Commercial Proposal.

8
 3 . B – FUNCTIONAL REQUIREMENT
SPECIFICATION
3.1 Functional Requirement
Specification

Req Requirement Response Remarks

No.
1 Implementation of all standard features of Advanced collection module  
2 Identify delinquent customers  
3 Obtain a snapshot of the customer's past payment history  
4 Review a customer's aging data  

5 View key customer collections metrics  

6 Track each delinquency as it moves through the collections lifecycle  
7 Support standard methods of payments that will quickly resolve the delinquent  
situation
8 Calculate collections scores for customers  
9 Plan and execute collections strategies to automate as much of the collections  
management process as possible
10 Plan and execute collections dunning plans to automatically send dunning  
notices and optionally, schedule dunning callbacks
11 Attach notes to a customer's records  
12 Determine the status of each transaction  
13 Assign business value to customers  
14 Execute collections management methods based on scores  
15 Delinquency, Broken Promise, and Strategy Actions Nodes on the Collector's  
Work Queue
16 Setup Collections Header  
17 Operational Data Views  
18 Profile Tab with Metrics Tables  
19 Detailed Collections Histories  
20 Automated Collections Scoring and Strategies Management  
21 Dunning Plans  
22 Payment Processing  
23 Promise to Pay  

9
 Req Requirement Response Remarks
No.
24 Dispute Handling  
25 Adjustment Processing  
26 Payment Reversals  
27 Correspondence  
28 Shared Notes  
29 Creating and Managing Tasks  
30 Attachments  
31 Collections Lifecycle Management  
32 If the same entity is operating as customer and supplier, system should be able  
to provide a holistic view of outstanding considering the Accounts payables due.

**Vendor is expected to demonstrate the features of advanced collection module and the demos will be
evaluated by mobitel

10