Telecommunications Business Information Model

A telecom operator's data is really two businesses layered on top of each other: a commercial business built on subscribers, accounts, and products, and a network business built on assets, services, and usage. This Business Information Model maps both — the foundational, transactional, and informational entities that connect them — as an editable Word document you can adapt to your own naming conventions and architecture standards.

Two Businesses, One Data Model

In telecom, the commercial view of the business and the network view of the business are both real, and they rarely line up one-to-one, which is where generic data models quietly fall apart. An account can carry multiple subscribers and lines — think family or enterprise plans — and a subscriber can move across accounts over time as numbers get ported, plans change, or ownership transfers. The rate plan a customer buys is a commercial construct that has to map to one or more underlying network services — exactly the distinction that generic models tend to collapse into a single 'product' entity. Usage itself — call detail records, data sessions — is a high-volume transactional entity that feeds billing but isn't the same entity as the invoice it eventually produces. Numbers and IP addresses behave like reference data with their own reservation and porting lifecycle, not simple foreign keys on a customer record.

What's Inside

• Foundational entities: Party, Account, Subscriber/Line, Product Catalog, Network Asset, Number/Identifier Inventory
• Transactional entities: Service Order, Network Provisioning Order, Usage Event (CDR/data session), Billing/Invoice, Trouble Ticket
• Informational entities: Usage Aggregates, Churn Indicators, Network Performance, Customer Lifetime Value
• Entity relationship diagram linking commercial (BSS) and network (OSS) entities
• Delivered as a fully editable Word document

How Teams Use It

• As a starting point for a subscriber or account data model in a CRM or billing consolidation project
• To scope master data management for party, account, and product catalog domains
• To align commercial (BSS) and network (OSS) data domains during integration planning
• As a shared reference when onboarding architects or vendors to how the business is structured

Who It's For

Data architects, business architects, and IT leaders at telecom operators, MVNOs, and the vendors serving them — anyone who needs a defensible starting point for BSS/OSS data architecture or a customer data model initiative.