CSP Integration: Timeline

Contents

• Overview
• CSP Integration Task Timelines
• Revision History

Overview

This topic contains communications service provider (CSP) integration task timeline information for CSPs when a new over-the-top (OTT) provider onboards with MarketONE for the CSP.

The following table contains descriptions of RACI codes that are used in this topic (see the RACI column in the table under the CSP Integration Task Timelines section):

Code	Description
R	The person responsible for the completion of the tasks that constitute the project.
A	The person accountable for the successful completion of the entire project. This accountability consists in reviewing the work that the responsible person provides once the work is finished, and then giving technical sign-off for it.
C	The person consulted whose advice on the project is sought because they are a subject matter expert (SME).
I	The person informed (kept up-to-date) on the progress of the project.

CSP Integration Task Timelines

The following table contains CSP integration task timeline information for CSPs when a new OTT provider onboards with MarketONE for the CSP.

Consider the following assumptions for this CSP integration task timeline:

• The CSP is already integrated with MarketONE.
• The commercial agreement has been signed by the OTT provider with both Amdocs and the CSP.
• The CSP and the OTT have already agreed upon charging for each product.
• The OTT provider has submitted their OTT Onboarding: Checklist.
• The standard cloud SaaS model and MarketONE APIs are used in the CSP-specific customization.
• There are no major roadblocks for the CSP to accomplish the necessary integration tasks.

Note: Under the Timeline column in the following table, 5 days is equal to 1 work week.

Milestone	Task	RACI			Timeline
		CSP	Amdocs	OTT
CSP information readiness	The CSP provides the charging code for each product the OTT offers. Note: The charge code is used by the CSP's BSS system to process the charge on bill.	R, A	I	A	1 day
	The CSP and the OTT agree on refund handling (if applicable).	R, A	C, I	R, A	1 day
	The CSP provides Amdocs with settlement rules: partner revenue share and taxation. The CSP provides Amdocs with eligibility rules: eligibilities from BSS account type, account status, platform, brand, and user type; and pre-configured eligibilities from M1, no change: spending limit (daily and monthly).	R, A	I	I	2 days
	The CSP and the OTT define and agree on the product description (this description is passed in as a parameter in the POST /transaction call and will show as is in the customer's billing).	R, A	I	R, A	2 days
	Amdocs presents the reports to the CSP to show what is coming for the new OTT.	A	R, A		1 day
CSP environment readiness	The CSP provides the OTT with a testing environment (if a separate environment is required).	R, A	I	I	5 days
Environment set up by Amdocs	Amdocs prepares the metadata of the new OTT in the pre-production environment by pointing to a different CSP testing environment (if required), configuring the charge code, creating settlement rules (revenue split, taxation etc), and defining eligibility rules, if applicable (account type, account status etc).	I	R, A		5 days
Test case preparation	Amdocs provides standard integration test cases to the OTT. The CSP provides mobile numbers to be used in the testing.	R, A	R, A	C, I	2 days
Integration testing	Integration testing is conducted between the OTT and the CSP (also covered in OTT Integration: Timelines).	I	I	R, A	2 days
Production readiness testing	Amdocs provides the production environment with all new OTT settings and configurations.	I	R, A	I	2 days
	The CSP has the production environment ready for product verification testing (PVT).	R, A	I	I
	The CSP provides a whitelisted phone number. PVT is conducted. The CSP verifies the reports for the new OTT and its products.	R, A	I	RA
Total:					5 calendar weeks

Revision History

Version	Description
2020.08	Added this topic.