10.418 min read

SLA, Contracts & Pricing Models

In consumer BSS, pricing is relatively straightforward — a customer picks a plan, pays monthly, and the SLA is implicit ("best effort" for most residential services). In enterprise BSS, contracts, SLAs, and pricing models are first-class entities that directly shape order management, billing, fulfillment, and assurance processes. Getting these wrong means revenue leakage, customer churn, and contractual penalties.

This section covers the three pillars of enterprise commercial management: Service Level Agreements (SLAs) that define quality commitments, contracts that formalise commercial relationships, and pricing models that determine how enterprise customers are charged. Together, these form the commercial backbone of any B2B BSS platform.

Why SLA Management Is Critical for Enterprise BSS

Unlike consumer services where "best effort" delivery is the norm, enterprise customers negotiate explicit service quality commitments backed by financial penalties. A bank running its trading platform over an MPLS network or a hospital relying on cloud-hosted patient records cannot tolerate ambiguity in availability, latency, or restoration times. SLAs translate these business requirements into measurable, enforceable parameters.

Revenue protection: Enterprise contracts worth millions per year include penalty clauses (SLA credits) triggered by breaches — accurate SLA tracking prevents unnecessary payouts
Operational prioritisation: When multiple incidents occur simultaneously, SLA tiers determine which customers get resources first — without SLA data, assurance teams operate blind
Contract renewal leverage: Historical SLA performance data is a key input to contract renewal negotiations — demonstrating consistent over-performance justifies premium pricing
Regulatory compliance: In regulated industries (finance, healthcare, government), SLA compliance may be a legal requirement, not just a commercial one
Differentiation: Tiered SLAs allow operators to create premium service tiers that command higher margins without deploying fundamentally different infrastructure

Service Level Agreement (SLA)

A formally negotiated agreement between a service provider and an enterprise customer that defines measurable service quality targets (availability, performance, restoration time), the measurement methodology, reporting obligations, and the commercial consequences (penalties or credits) of failing to meet those targets. In TM Forum terms, an SLA is associated with a Product instance and references Service Quality parameters defined in the Service Catalog.

SLA Tiers and Service Quality Parameters

Most operators define a set of standard SLA tiers that enterprise customers can select from, rather than negotiating every parameter individually. Each tier bundles availability, response time, resolution time, and penalty terms into a coherent package. Custom SLAs are available for the largest enterprise customers but are expensive to manage.

Standard Enterprise SLA Tiers

Parameter	Bronze	Silver	Gold	Platinum
Monthly Availability	99.5% (3.6h downtime)	99.9% (43min downtime)	99.95% (22min downtime)	99.99% (4.3min downtime)
Incident Response Time	4 hours	2 hours	1 hour	15 minutes
Incident Resolution Time	24 hours	8 hours	4 hours	2 hours
Service Restoration Target	Next business day	8 hours (24/7)	4 hours (24/7)	1 hour (24/7)
Proactive Monitoring	No	Basic threshold alerts	Advanced with trend analysis	Dedicated NOC monitoring
Change Window	Standard (72h notice)	Standard (48h notice)	Priority (24h notice)	Emergency (4h notice)
Penalty (Credit per Breach)	5% of monthly fee	10% of monthly fee	15% of monthly fee	20% of monthly fee + escalation
Maximum Monthly Credit Cap	25% of monthly fee	50% of monthly fee	75% of monthly fee	100% of monthly fee
Reporting	Monthly summary	Weekly report	Daily dashboard access	Real-time portal + monthly exec review
Typical Use Case	SME branch connectivity	Mid-market corporate WAN	Enterprise data centre links	Financial services, critical infra

Availability vs Restoration vs Resolution

These are commonly confused. Availability is the percentage of time the service is operational over a measurement period. Restoration time is how quickly the service is brought back to a working state after an outage. Resolution time is how quickly the root cause is identified and permanently fixed (which may be longer than restoration if a temporary workaround is applied). An SLA may specify all three independently.

Intermediate

SLA Breach Detection and Credit Calculation

When a service fails to meet its SLA targets, the BSS must detect the breach, calculate the appropriate financial credit, and apply it to the customer's account — ideally automatically.

SLA breach handling involves a chain of systems: the assurance platform detects a service degradation or outage, the SLA management system evaluates the incident against the customer's SLA parameters (was availability breached? was restoration time exceeded?), the penalty engine calculates the credit amount based on the contractual formula, and the billing system applies the credit to the next invoice. Mature operators automate this entire chain. Less mature operators rely on manual processes where the customer must file a claim, a support agent investigates, and finance manually issues a credit — a process that can take weeks and is error-prone.

SLA Breach Example

An enterprise customer on a Gold SLA ($10,000/month) experiences a 6-hour outage on their primary data centre link. Gold SLA guarantees 99.95% availability (max 22 minutes downtime/month) and 4-hour restoration. Two SLA breaches occurred: availability (6 hours > 22 minutes) and restoration time (6 hours > 4 hours). Per the contract: availability breach = 15% credit ($1,500) + restoration breach = additional 10% credit ($1,000) = total credit of $2,500 applied to the next invoice. The SLA management system records both violations and triggers the credit automatically.

TMF623 — SLA Management API

TMF623 provides a standardized API for creating, querying, and managing Service Level Agreements. Key resources include SLA (the agreement itself, linking parties, services, and quality parameters), SLAViolation (recorded breach events), and SLAObjective (individual measurable targets within an SLA). The API supports lifecycle management of SLAs from draft through active to terminated states, and enables automated violation detection and credit calculation when integrated with assurance systems.

TMF645 — Service Quality Management API

TMF645 defines how service quality metrics are captured, aggregated, and reported. It provides standardized resources for ServiceLevelObjective (target thresholds for specific quality parameters), ServiceLevelSpecification (templates defining which objectives apply to a service type), and ServiceQualityConsequence (actions triggered when thresholds are breached). TMF645 is the bridge between the network/service monitoring world and the commercial SLA world — it translates raw performance data into SLA-relevant quality measurements.

Contract Lifecycle Management

Enterprise contracts are not simply "terms and conditions checkboxes" as they are in consumer BSS. They are complex, negotiated legal instruments that govern multi-year relationships often worth millions in annual recurring revenue. The contract lifecycle in enterprise BSS spans negotiation, execution, management, renewal, and termination — with each phase requiring specific system capabilities.

Enterprise Contract Lifecycle

Opportunity & Qualification

CRM

Sales identifies a contract opportunity and qualifies the customer need. Initial scoping determines which products, services, and SLA tiers are likely required. A preliminary commercial model is drafted. RFP/RFI responses may be required for larger deals.

Solution Design & Pricing

CPQ / Solution Design Tool

Technical pre-sales designs the solution (network topology, service mix, capacity). CPQ generates a formal quote with contract terms, pricing schedules, SLA commitments, and early termination clauses. Multiple pricing iterations are common.

Negotiation & Approval

Contract Management / CRM

Commercial and legal teams negotiate contract terms with the customer. Custom SLA parameters, bespoke pricing, liability caps, and special conditions are agreed. Internal approval workflows (pricing authority, legal review, finance sign-off) must be completed before the contract can be executed.

Execution & Activation

Contract Management / COM / Billing

Contract is signed by both parties. The executed contract triggers order creation in COM for the initial service portfolio. SLA parameters from the contract are registered in the SLA Management system. Billing accounts and payment terms are configured.

In-Life Management

COM / SLA Mgmt / Billing

During the active contract period, MACD operations add, change, or remove services within the contract scope. SLA performance is continuously monitored and reported. Usage-based charges are metered and invoiced. Contract amendments may be executed for scope changes that alter commercial terms.

Review & Renewal

CRM / Contract Management

As the contract approaches its end date, a renewal process begins. Historical SLA performance, usage trends, and customer satisfaction data inform the renewal offer. Pricing may be adjusted based on market conditions, volume commitments, and competitive pressure. Auto-renewal clauses may apply if no action is taken.

Termination & Churn

COM / Billing / Contract Management

If renewal is not agreed, the contract enters termination. Early termination may incur penalty charges. A structured wind-down plan ensures orderly disconnection of services, return of equipment, settlement of outstanding invoices, and data migration support. Customer data retention policies apply.

Contract vs Order vs Subscription

In enterprise BSS, these are distinct entities. A contract is the commercial agreement defining terms, duration, and pricing rules. An order is a request to provide, change, or remove services under that contract. A subscription (product instance) is the actual running service that exists as a result of fulfilled orders. One contract may span hundreds of orders and thousands of active subscriptions. The contract is the commercial umbrella; orders are the mechanism; subscriptions are the result.

Enterprise Pricing Models

Enterprise pricing is significantly more complex than consumer pricing. While a consumer might pay a fixed monthly fee for broadband, an enterprise customer may combine per-seat licensing, per-site connectivity charges, tiered volume discounts, usage-based overage fees, and one-time installation charges — all within a single contract. The BSS must model, calculate, and invoice all of these correctly.

The per-seat (or per-user) pricing model charges based on the number of individual users or endpoints consuming a service. Common for collaboration platforms (UCaaS), security services, and managed desktop solutions.

Charge unit: individual user licence or named endpoint
Billing: monthly recurring charge multiplied by active seat count
MACD impact: adding/removing users triggers billing adjustment mid-cycle
Discount pattern: volume tiers — e.g., 1-100 seats at full price, 101-500 at 10% discount, 500+ at 20% discount
Challenges: tracking active vs provisioned vs suspended seats; handling mid-month changes (pro-rata calculation)

Per-Seat Example

A managed UCaaS offering priced at $25/seat/month. The enterprise has 350 active seats. Monthly charge: 100 x $25 = $2,500 (tier 1) + 250 x $22.50 = $5,625 (tier 2, 10% discount) = $8,125/month. When the customer adds 30 seats mid-month, pro-rata charges apply for the remaining days.

Source-of-Record Ownership

In enterprise BSS, contract, SLA, and pricing entities must have clearly defined ownership. Without clear SoR boundaries, enterprise billing disputes become unresolvable, SLA credit calculations are unreliable, and contract amendments introduce data conflicts across systems.

Contract, SLA & Pricing Source-of-Record

Entity	System of Record	System of Engagement	System of Reference	Notes
Enterprise Contract	Contract Management System	CRM (sales negotiation)	Product Catalog (eligible offerings)	Legal instrument with commercial terms, duration, and scope. CLM system is authoritative.
SLA Definition	SLA Management (TMF623)	Contract Management (negotiated terms)	Service Quality Spec (TMF645)	SLA parameters are defined during contract negotiation but managed operationally by the SLA system.
SLA Violation / Credit	SLA Management (TMF623)	Assurance / NOC (detection)	Billing (credit application)	Violations are detected by assurance, recorded in SLA Mgmt, and credits applied via billing.
Pricing Rules & Rate Cards	Product Catalog / Pricing Engine	CPQ (quote generation)	Contract (negotiated overrides)	Standard pricing lives in the catalog; contract-specific overrides are stored against the contract.
Contract-Specific Discounts	Contract Management System	CPQ (applied at quote time)	Billing (applied at invoice time)	Negotiated discounts are owned by the contract and referenced by billing during invoice generation.
Usage Metering Data	Mediation / Rating Engine	Network Elements (raw CDRs/UDRs)	Billing (rated records)	Raw usage is collected from the network, mediated, rated against pricing rules, and sent to billing.
Invoice / Bill	Billing System (TMF678)	Customer Portal (presentment)	Contract (terms for dispute resolution)	The billing system generates the definitive invoice. Customer portal provides self-service access.

Section 10.4 Key Takeaways

Enterprise SLAs are formal, negotiated commitments with financial penalties — not "best effort" promises
Standard SLA tiers (Bronze through Platinum) allow scalable service differentiation without per-customer customisation
The contract lifecycle spans opportunity, design, negotiation, execution, in-life management, renewal, and termination — each phase requires dedicated BSS capabilities
Contracts, orders, and subscriptions are distinct entities: the contract is the commercial umbrella, orders are the mechanism, subscriptions are the result
Enterprise pricing models (per-seat, per-site, tiered, usage-based, hybrid) are far more complex than consumer pricing and require sophisticated rating and billing engines
TMF623 (SLA Management) and TMF645 (Service Quality Management) provide standardised APIs for managing SLAs and linking them to network-level quality measurements
Clear source-of-record ownership for contracts, SLAs, pricing, and billing is essential to avoid enterprise billing disputes and SLA credit errors