πŸ”­Project Scope

In-Scope Items (EBS Responsibilities)

The following activities and deliverables are explicitly within the scope of work for the Vendor (EBS) during the OTA DOI Proof of Concept (POC) and implementation phases.

1.1. Solution Deployment & Integration

  • OTA DOI Solution Delivery: Provisioning of the Push Service Manager (PSM) capable of controlled message delivery with a high success rate (>98%).

  • Integration: Development and deployment of APIs and connectors to integrate the PSM with MTNN's existing OTA platform, HSM, and VAS provisioning systems (MSAP).

  • Technical Setup: Installation and configuration of the solution within MTN’s designated test and production environments.

1.2. POC Execution & Support

  • POC Management: Execution of the POC for selected VAS products over a defined 3-month duration.

  • Technical Support: Provision of 24/7 technical support and SLA compliance during the POC and post-implementation phases.

  • Performance Optimization: Tuning the solution to meet the target latency (<3s) and uplift (>20%) metrics.

1.3. Monitoring & Reporting

  • Tooling: Delivery of monitoring dashboards and reporting tools for real-time tracking of performance, latency, and delivery success.

  • Reporting: Submission of weekly performance reports and a comprehensive Final POC Report covering technical and commercial outcomes (ROI analysis).

Out-of-Scope Items (MTN Responsibilities)

The following items are excluded from the Vendor's scope or are explicitly the responsibility of MTN Nigeria or third parties.

2.1 Infrastructure & Environment

  • Hardware/VM Provisioning: MTNN is responsible for providing the necessary development, UAT, and Production environments (e.g., Virtual Machines, physical hardware) for the solution deployment.

  • Network Connectivity: Provisioning of necessary network paths, firewall rules, and opening of ports between the EBS PSM cluster and MTNN's internal segments (OTA, SMSC, MSAP) is an MTNN responsibility.

2.2 Upstream & Downstream Systems

  • Legacy System Upgrades: Modifications or upgrades to MTNN's existing OTA/HSM or MSAP platforms to handle the target 250 TPS load are out of scope for the vendor, unless a specific joint performance tuning plan is initiated.

  • API Exchange: Completion of dependent tasks on key systems like the API exchange is a prerequisite managed by MTNN.

2.3 Business Logic & Segmentation

  • Subscriber Segmentation: Definition and provision of the specific subscriber segments/numbers to be used for the POC.

  • 3rd Party Partner Management: While the solution allows 3PP initiation, the commercial management and onboarding of those 3rd parties onto the MTN network is out of scope.

Last updated