Business Context:

Telecom providers frequently renew standalone services such as connectivity or value-added plans to ensure uninterrupted customer service. This use case demonstrates how a telecom standalone service is renewed while preserving service continuity by retaining the existing asset end date logic.

Overview:

This use case describes the renewal of a standalone telecom service with multiple charge types (for example, recurring service fees, surcharges, etc). It explains how renewal dates are derived and how the service asset status changes during the renewal lifecycle.

Scenario:

A standalone telecom service asset, Enterprise Data Connectivity Service, includes four different charge types. The cart has been finalized and an order has been generated. The service appears as asset line items on the Quote/Proposal and under the customer Account in Installed Products. The service is now renewed using the Renewal Option: Retain Asset End Date.

When the Renewal Option = Retain Current Asset End Date, the system derives the renewal dates using Asset End Date + 1 day by default to preserve service continuity and prevent overlap. The behavior is intentional and supports standard telecom and subscription-based renewal practices. This ensures:

• No Service Gap

  • The original asset is valid through its end date (for example, 07/25/2026).
  • Starting the renewed asset on 07/26/2026 ensures uninterrupted service with no break between terms.
• No Date Overlap

  • If the renewed asset started on the same end date, both assets would be active on the same day.
  • This could result in double entitlement, duplicate billing, or rating conflicts—especially critical in telecom services.
• Clear Contract Term Boundaries

  • Telecom contracts are typically modelled as inclusive end dates.
  • Using End Date + 1 creates clean, non-overlapping contract terms:
    • Old term: 07/26/2025 – 07/25/2026
    • New term: 07/26/2026 – 07/25/2027
• Consistent Billing and Rating

  • Billing systems rely on precise start and end dates for proration, rating, and invoice generation.
  • This approach avoids double-billing or missing charges during renewal transitions.