OSS/BSS Modernisation in Nigeria and Africa: A Buyer’s Roadmap

OSS/BSS modernisation should solve a defined operating or commercial problem. An operator replacing fragmented systems needs to know which services, records and workflows will improve, how migration will be controlled and who will run the new environment. Wigmore Trading accepts enquiries for telecom procurement and integration planning in Nigeria and Africa. The proposed software, specialist capability and delivery scope must be confirmed for each project.

Understand the difference between OSS and BSS

Operations support systems commonly address network and service operations, while business support systems address commercial activities such as customers, products and billing. The boundary varies by architecture and supplier. Map responsibilities in your actual environment instead of assuming that a product called a telecom platform includes every function. A CRM, billing engine and network-management system may remain separate components.

Set outcomes before selecting a vendor

Identify the specific failures: delayed service activation, inconsistent customer records, manual reconciliation or difficult incident resolution. Measure the current position and agree realistic acceptance criteria. “Next generation” and “carrier grade” need measurable requirements for capacity, availability, recovery and operating support. A technology label alone cannot establish that a system meets your network’s needs.

Choose a phased migration where it fits

A legacy OSS or BSS migration can involve data cleansing, interface changes, parallel operation and controlled service transitions. Define which records are authoritative and how errors are corrected. Reconcile customer, service and financial information before and after a trial migration. Avoid accepting a successful file import as proof that complete business processes work. Qualified teams should own cutover and rollback decisions.

Evaluate integration evidence

Ask suppliers to demonstrate representative workflows and disclose custom development. The TM Forum Open API programme provides an industry reference for service-lifecycle and partner integration. Specify the interfaces and versions your project needs; a general claim of standards support does not prove interoperability with your existing systems. Confirm any certification claim independently.

Compare the full operating cost

Include licence or subscription fees, integration, migration, hosting, training, support and exit costs. Determine who operates the platform, manages upgrades and resolves cross-vendor incidents. For SaaS, confirm data access, residency requirements, export capability and termination support. A lower initial quote can shift substantial costs into implementation or day-to-day operations.

Prepare an actionable enquiry

Send Wigmore a redacted system map, markets served, main pain points, required functions, expected scale and target dates. State whether you need vendor research, a requirements exercise, quotation comparison or related infrastructure sourcing. We can help organise the procurement brief and clarify available specialist dependencies. Do not include subscriber records, credentials or confidential network diagrams in an open initial message.

What should a first proposal contain?

Ask for a clear scope, responsibility matrix, implementation assumptions, acceptance plan and exclusions. Identify the legal provider and any subcontractors. A discovery discussion should narrow uncertainty and produce a usable next step; it should not be presented as a guaranteed migration date or an already licensed Wigmore software platform.