Begin with the service journey
Business support systems give a connectivity provider the commercial processes behind its services. A customer selects an offer, an order records the request and several applications may participate before the service can be used. The visible customer journey is only as clear as those software hand-offs.
BSS design therefore starts with questions about responsibility. Which application owns the customer relationship? Where is the offer defined? What records the subscription? Which component can prove that fulfilment has finished?
Separate the records that change at different times
A customer can exist before making a purchase. A product offering can be withdrawn while subscriptions based on it remain active. An order can complete while a later billing correction is still being investigated. Giving those concepts distinct records makes their relationships easier to maintain.
The practical link is a set of stable identifiers and agreed lifecycle rules. These let a CRM, a shared repository and an orchestration layer exchange enough context to perform their own jobs without each becoming a duplicate of the others.
Choose a boundary small enough to deliver
Modernization does not require every system to change at once. A useful first slice might be a new-customer order or a business account amendment. It should include the initiating channel, the source records, the fulfilment action and the status returned to the user.
For each hand-off, document the request, the completion evidence and the owner of an exception. This turns an architectural diagram into something that can be implemented and tested.
- Identify the authoritative customer and product records.
- Define the order states visible to staff and customers.
- Agree how provisioning and charging systems exchange status.
- Reconcile the resulting subscription against the accepted request.
Use product fit to guide the next discussion
We bring three products to these boundaries: Telco CRM, the Order Orchestration Platform and the Central Product and Customer Repository. Their fit is best explored through a real business journey and the applications already supporting it.
Connect the business view to OSS
Operations support systems handle the service and resource processes behind fulfilment and ongoing support. BSS needs a clear hand-off into those processes and a reliable way to receive activation results, service state and information relevant to customer care.
Define the relationship between the commercial product, the service instance and the resources used to deliver it. This gives both sides a shared way to trace an order, investigate a discrepancy and explain the result to the customer.
Technical references
Primary references for the concepts discussed here.