OTT Integration: Timelines

Overview
OTT Integration with MarketONE (Mock SP)
OTT Integration with MarketONE (Real SP)
Revision History

Overview

This topic contains over-the-top (OTT) provider onboarding integration timelines for OTTs integrating with MarketONE (M1) with a mock service provider (SP), and with a real SP.

The following table contains descriptions of RACI codes that are used in this topic (see the RACI columns in the two tables in the OTT Integration with MarketONE (Mock SP) and the OTT Integration with MarketONE (Real SP) sections below).

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.

Note: These OTT integration timelines assume that the OTT has not been previously integrated with M1.

OTT Integration with MarketONE (Mock SP)

The following table contains timeline information concerning an OTT provider fully integrating with M1 using a mock SP.

Consider the following assumptions for this mock SP OTT integration timeline:

The OTT provider has signed the commercial agreement.
The OTT provider has the required resources for the integration.
The OTT provider is committed to the timeline.
There are no major roadblocks to the integration.

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

Milestones	Tasks	RACI			Timeline
		OTT	Amdocs	SP
M1 Documentation is shared with the OTT provider.	Share M1 integration documentation with the OTT provider, including the OTT Onboarding: Checklist document checklist on the MarketONE Developer Portal.	I	R, A		1 day
OTT provider reviews the documentation.	Review the M1 documentation (OTT provider task). Return answers from the document checklist (OTT provider task).	R, A			5 days
Amdocs conducts a Q&A session with the OTT provider.	Conduct a question and answer discussion based on the reviewed and received documentation. Present M1 out-of-the-box (OOB) use cases to the OTT provider.	R, A	R		5 days
Use cases are finalized.	Review the terms of conditions, and finalize the use cases.	R, A	R		Included from above
Environment is prepared.	Set up an OTT admin in M1. Set up a developer for the MarketONE Developer Portal. Set up an OTT organization and OTT product(s) in M1.	I	R, A		3 days
	Prepare and handover the M1 sandbox environment (in which the OTT can integrate and test against the mock SP).	I	R, A
	Generate and access API keys in the MarketONE Developer Portal.	I	R, A
OTT provider gains familiarization with the environment.	Explore the M1 sandbox environment, and experiment with the MarketONE APIs.	R, A	C		5 days
Design document is created and uploaded for approval.	Create and upload the solution design document for approval (via either email or the MarketONE Developer Portal).	R, A			5 days
	Provide test cases for Amdocs to review.	R, A	I
Design document receives technical sign off.	Review and approve the design document and the test cases that are supplied by the OTT provider (Amdocs task).	I	R, A		5 days
OTT managed flow is developed.	Complete the development and configuration of the flow (OTT developer task).	R, A			5 days
M1 managed flow is developed.	Set up the callback API. Set up the API key for the mock SP.	R, A	R		2 days
	Complete the development and configuration of the flow (OTT developer task).	R, A			5 days
Development is completed.	Exchange SSL certificates. Enable IP whitelisting (if required).	R, A	R, C		1 day
OTT provider is fully integrated with the mock CSP.	Test and validate the MarketONE-OTT integration in the sandbox with the mock SP for the OTT managed flow.	R, A	C		5 days
	Test and validate the MarketONE-OTT integration in the sandbox with the mock SP for the M1 managed flow.	R, A	C		5 days
OTT integration is certified.	Certify the OTT integration with M1.	I	R, A		0 days
Total:	Note: This total assumes only one type of purchase flow (either OTT managed or MarketONE managed).				52 days

OTT Integration with MarketONE (Real SP)

The following table contains timeline information concerning an OTT provider fully integrating with MarketONE using a real SP.

Consider the following assumptions for this real SP OTT integration timeline:

The OTT provider is fully integrated with MarketONE.
MarketONE environments are already connected with the corresponding SP environments.
The timeline estimate from the SP side is documented separately.