BSS Assessment
A BSS assessment in three weeks.
Ingests workshops, catalogues and vendor documents, maps them to TM Forum standards and produces the full assessment in three weeks.
- Solves
- BSS assessments that take months and date quickly
- Used by
- BSS programme leads and architects
- You receive
- As-is and to-be architectures, a gap map, a rationalisation view and a roadmap
- Proof
- Telco BSS programme: 3 weeks against a 3-month plan
The problem
Traditional BSS assessments take months and go out of date immediately.
Building a reliable view of applications, integrations, capabilities and dependencies is manual work, and the findings rarely trace back to evidence.
Complex, fragmented BSS landscapes
- Generations of CRM, billing, ordering, catalogue and provisioning systems coexist across business units.
- Legacy and strategic platforms overlap, with duplicated capabilities.
- Hundreds of interfaces and APIs connect them, and journeys span many systems.
Manual discovery and disconnected evidence
- Teams rely on workshops, interviews, spreadsheets, inventories and existing documents.
- Ownership, functionality and integration dependencies are hard to verify.
- Findings are consolidated by hand, with little traceability to evidence.
Static outputs, limited transformation visibility
- Months of analysis end in slides, spreadsheets and reports.
- The current-state picture dates as soon as systems change.
- Target architecture and roadmaps drift away from ongoing delivery.
Late discovery of vendor gaps and dependencies
- Vendors are often chosen before capability requirements are understood.
- Customisation and add-ons get mistaken for standard capability.
- Dependencies surface during implementation, as change requests, cost and delay.
to build a point-in-time BSS assessment, often before vendor selection and transformation planning can be finalised
Why it’s faster.
Assessment closes in weeks
Three weeks against a three-month plan for the same scope.
Every finding traces to its source
Every finding carries a link to the sentence, catalogue row or document it came from.
The model stays live
The output is a queryable model that updates as the programme moves.
Vendor scope is settled upfront
The gap map marks every capability as covered, partial or not covered before contract signature.
BSS Assessment runs on the same model as the rest of EcoGenie, so the BSS picture stays connected to the architecture, initiative and delivery views.
How it works
Four steps, from ingestion to publishing.
Workshop sessions, transcripts and the EA catalogue go in. A standards-aligned BSS architecture comes out.
Ingest
Workshop sessions, transcripts, the EA catalogue, vendor documentation and code. Nothing is re-keyed by hand.
Map to standards
Every capability, function, application and interface aligned to the industry reference models.
Cross-check
Session-derived and catalogue-derived mappings compared against each other and against vendor scope.
Publish
Architectures, capability and gap maps, rationalisation and roadmap, published into a live model.
Ingests
- Code
- Confluence & Jira
- Excel
- MCP connectors
- Screenshots
- Teams & transcripts
Produces
- As-is architecture
- To-be architecture
- Capability and gap map
- Application rationalisation
- API realisation view
- Requirements register
- Ownership map
- Phased roadmap
Mapped to the industry reference models
TM Forum ODA
Functional domains & components
TM Forum Open APIs
Realisation & conformance
TAM
Application framework functions
SID
Information & data ownership
eTOM
Business processes
Traceability
Every finding has a source.
Each finding links to the session, catalogue entry or document it came from.
Source
Workshop 4 transcript, 00:41
“Prepaid top-ups are rated on a separate platform.”
Finding
Prepaid rating runs outside the convergent charging system
Capability
TM Forum ODA: Rating and charging
Gap status
Partial
Integration with the converged core needed
Roadmap item
Phase 2
Converge prepaid rating onto the core
Ask the assessment
Query findings by capability, system or vendor, for example every partial gap in Core Commerce.
Mapped to standards
Findings map to TM Forum ODA, Open APIs, TAM, SID and eTOM through EcoGenie for Telco.
The deliverable set
Eight connected outputs.
As-is and to-be architectures and the gap between them, produced as one connected set.
As-Is architecture
The estate as it actually runs
To-Be architecture
Standards-aligned target state
Capability & gap map
Covered · partial · not covered
Application rationalisation
Replace · consolidate · retain · retire
API realisation view
Which systems realise which Open APIs
Requirements register
Filterable, by capability domain
Ownership map
Who owns what across the business
Phased roadmap
Sequenced by dependency and value
Example output
The estate, read against TM Forum ODA.
Each tile shows how well today’s estate realises a capability, so gaps and overlaps are visible at a glance.
Engagement Management
- Digital channels: Strongly realised
- Campaign & offer: Partially realised, gap
- Interaction management: Partially realised, gap
- Journey orchestration: Thin or absent
- Personalisation: Thin or absent
- Loyalty & rewards: Thin or absent
Party Management
- Customer 360: Partially realised, gap
- Party role & account: Strongly realised
- Agreement management: Partially realised, gap
- Privacy & consent: Thin or absent
- Partner onboarding: Partially realised, gap
- Identity & access: Strongly realised
Core Commerce
- Product catalogue: Strongly realised
- Product ordering: Strongly realised
- Quote & CPQ: Partially realised, gap
- Billing & invoicing: Strongly realised
- Payment & collection: Strongly realised
- Usage rating: Strongly realised
Production
- Service catalogue: Thin or absent
- Service orchestration: Partially realised, gap
- Resource inventory: Partially realised, gap
- Activation & config: Strongly realised
- Assurance & fault: Partially realised, gap
- Workforce management: Thin or absent
Intelligence & OSS
- Data warehouse: Partially realised, gap
- Analytics & reporting: Partially realised, gap
- AI decisioning: Thin or absent
- Revenue assurance: Partially realised, gap
- Fraud management: Partially realised, gap
- Data governance: Thin or absent
capabilities strongly realised
partially realised, gaps remain
thin or absent: build, buy or keep the legacy system
capabilities across 5 ODA domains
- Strongly realised
- Partially realised, gap
- Thin or absent
Example output
As-is versus to-be, by TAM domain.
The estate read through the TM Forum Application Framework, showing what each domain serves today and what should serve it next.
| Framework block | As-is · typical operator landscape | To-be · standards-aligned target |
|---|---|---|
| Customer Management | Partial, needs integration or a retained system: Several CRMs by segment and channel. No single enterprise Customer 360. | Target state covered by the converged core: One customer, party and account model behind every channel. |
| Sales & Order Management | Gap or weak today: Separate fixed and mobile order stacks; CPQ and POS run their own flows. | Target state covered by the converged core: Converged order capture and orchestration across all product lines. |
| Product & Offer Catalog | Gap or weak today: Per-silo catalogues, duplicated products, long time-to-market. | Target state covered by the converged core: One master catalogue driving offer composition, bundling and pricing. |
| Service Fulfilment & Provisioning | Partial, needs integration or a retained system: Provisioning via ESB point-to-point plus manual and RPA steps. | Target state covered by the converged core: Catalogue-driven provisioning and activation over Open APIs. |
| Billing & Revenue Management | Gap or weak today: Distributed rating and billing across two or more vendor stacks. | Target state covered by the converged core: Convergent rating, mediation, billing, payment and collection. |
| Revenue Assurance & Fraud | Partial, needs integration or a retained system: Broad control coverage, largely manual and outside the core. | Partial, needs integration or a retained system: Retained or new-build, integrated to the core, not inside it. |
| Credit & Collections | Partial, needs integration or a retained system: External vetting, dunning and third-party debt collectors. | Partial, needs integration or a retained system: Core handles limits, vetting and dunning; bad debt stays partner-side. |
| Partner & Commission | Partial, needs integration or a retained system: Dealer, franchise and BPO commissions in a separate estate. | Partial, needs integration or a retained system: Party and organisation management in core; commission engine retained. |
| Digital Channels & Engagement | Gap or weak today: Siloed apps, portal, USSD and chat with limited self-service. | Target state covered by the converged core: Digital experience layer over Open APIs, with CVM and personalisation. |
| Enterprise & Common (Data / EA) | Partial, needs integration or a retained system: Warehouse, marts and spreadsheets. No canonical or master data model. | Partial, needs integration or a retained system: Core information architecture plus a retained enterprise data fabric. |
- Target state covered by the converged core
- Partial, needs integration or a retained system
- Gap or weak today
Example output
One canonical API layer.
The TM Forum Open API set, under its official TMF names, between channels, the commercial core and the retained estate.
Party Management
- TMF629Customer: Served by the converged commercial core
- TMF632Party: Served by the converged commercial core
- TMF669Party Role: Served by the converged commercial core
- TMF666Account: Served by the converged commercial core
- TMF651Agreement: Served by the converged commercial core
- TMF683Party Interaction: Partial, core plus a retained system
- TMF672User Roles & Permissions: Partial, core plus a retained system
Core Commerce Management
- TMF620Product Catalog: Served by the converged commercial core
- TMF622Product Ordering: Served by the converged commercial core
- TMF637Product Inventory: Served by the converged commercial core
- TMF663Shopping Cart: Served by the converged commercial core
- TMF648Quote: Partial, core plus a retained system
- TMF671Promotion: Partial, core plus a retained system
- TMF676Payment: Served by the converged commercial core
Billing & Usage
- TMF678Customer Bill: Served by the converged commercial core
- TMF670Payment Method: Served by the converged commercial core
- TMF654Prepay Balance: Served by the converged commercial core
- TMF677Usage Consumption: Served by the converged commercial core
- TMF635Usage: Partial, core plus a retained system
- Collections: Partial, core plus a retained system
- Revenue assurance feeds: New-build or owned outside the core
Production
- TMF633Service Catalog: Partial, core plus a retained system
- TMF641Service Ordering: Served by the converged commercial core
- TMF638Service Inventory: Partial, core plus a retained system
- TMF640Service Activation: Served by the converged commercial core
- TMF634Resource Catalog: Partial, core plus a retained system
- TMF639Resource Inventory: Partial, core plus a retained system
- TMF621Trouble Ticket: New-build or owned outside the core
Engagement Management
- TMF681Communication: Partial, core plus a retained system
- Notification: Partial, core plus a retained system
- Federated identity: Partial, core plus a retained system
- Case / contact centre: New-build or owned outside the core
- Digital experience / UI: New-build or owned outside the core
- TMF646Appointment: Partial, core plus a retained system
- TMF680Recommendation: New-build or owned outside the core
Decoupling & Integration
- TMF688Event: Served by the converged commercial core
- TMF701Process Flow: Served by the converged commercial core
- Integration / middleware: New-build or owned outside the core
- Event mesh / topics: New-build or owned outside the core
- API gateway & security: New-build or owned outside the core
- Schema & contract registry: New-build or owned outside the core
- Conformance (Open API / CTK): New-build or owned outside the core
Intelligence Management
- TMF628Performance: Partial, core plus a retained system
- TMF921Intent: New-build or owned outside the core
- AI agent: New-build or owned outside the core
- Conversational AI / NLP: New-build or owned outside the core
- Knowledge: New-build or owned outside the core
- AI / ML model: New-build or owned outside the core
- Data & analytics: Partial, core plus a retained system
Enterprise & Platform
- TMF667Document: Partial, core plus a retained system
- Change: Partial, core plus a retained system
- EA & programme governance: New-build or owned outside the core
- Policy & security: New-build or owned outside the core
- ERP financials: Partial, core plus a retained system
- HR / workforce: Partial, core plus a retained system
- Facilities & budget: Partial, core plus a retained system
- Served by the converged commercial core
- Partial, core plus a retained system
- New-build or owned outside the core
See EcoGenie on your own architecture.
Tell us about your BSS estate. We’ll show you what an assessment finds in three weeks.