uplyst.Connect subscriptions, services and network resources.
Follow the relationship between what a customer ordered, how it was provisioned and the operating evidence behind its service.
From customer product to network resourceProduct, service and resource relationships
Customer product
The accepted commercial arrangement
Service instance
Realizes the product
Service instance
The delivered service configuration
Network resources
Support the service
From customer product to network resource
A customer buys a commercial product, which may be realized through several services and network resources. Those relationships can change as configurations, locations or offers evolve. When the records diverge, an operator may struggle to connect a customer complaint with the correct service instance or billing arrangement.
A contextual intelligence model links the commercial order, service inventory and supporting resources while preserving their distinct meanings. It can help a team investigate whether an issue concerns provisioning, service operation, inventory accuracy or the commercial record.
Investigate a customer service issue through its dependencies
A customer service issue can span the ordered product, active service instances, network observations and open trouble records. Bringing these records together gives the operations team the service history and commercial commitments relevant to its investigation.
| System context | Question it answers |
|---|---|
| Product and order | What was accepted for the customer? |
| Service inventory | Which service instances realize the product? |
| Resource and assurance | Which components and observations are relevant? |
| Billing and usage | Which commercial records need reconciliation? |
Catalog definitions and active services
A catalog describes an offered product; an inventory record describes a realized instance. Link both with their applicable versions and effective dates. An older customer arrangement may remain valid even after the current catalog changes, so the model needs to preserve the terms used when the order was accepted.
TM Forum's TMF620 Product Catalog API specifies how product catalog descriptions can be exchanged. Service inventory, network resources and billing have their own interfaces and data models.
Account for partial provisioning and inventory drift
A provisioning workflow can complete only part of an order or leave an inventory update delayed. Represent the intermediate state rather than forcing it into a simple active or inactive label. Track which system confirmed each transition and how an unresolved mismatch is investigated.
Subscriber and communications information can be sensitive. Apply the appropriate access boundaries to operational and commercial context. An investigation should expose the evidence needed for the role without making unrelated customer activity broadly available.
Follow service changes through the lifecycle
An amended order, partial activation or resource replacement can leave product, inventory and billing records at different stages. The customer's service position depends on which changes have actually completed.
Linking each transition to its source record helps operations teams locate a provisioning gap, reconcile a billing discrepancy and understand the service affected by a resource change.
Talk to us about your operations.
- Connect commercial products to realized service instances
- Expose inventory and provisioning mismatches
- Support service reviews with relevant operational evidence