Open APIs

Expand all | Collapse all

CustomerFacingServiceSpec Characteristic Queries

  • 1.  CustomerFacingServiceSpec Characteristic Queries

    Posted Aug 31, 2020 08:20
    Edited by Himanshu Sharma Sep 01, 2020 01:37
    Hi Team,

    We have queries regarding the customer facing service spec characteristics as below​.

    We have two type of offer Residential and Business. Both offer will have single product specification having below mentioned service.
       1) Voice
       2) Data
       3) International Roaming (IR)
    We want to make International roaming service optional for Residential offer and Mandatory for Business offer. We want to use Customer facing service spec characteristics for marking this as optional or mandatory.

    How can we override this characteristics as Product spec level? Could you please guide us.

    We are referring below structure which is not getting mapped with our requirement.

    ProductSpec characteristics translated to ServiceSpec characteristics

    Himanshu Sharma
    Sterlite Technology

  • 2.  RE: CustomerFacingServiceSpec Characteristic Queries

    TM Forum Member
    Posted Sep 06, 2020 04:57
    Hi Himanshu
    The picture you showed here is an example from a SID document, yet you are posting in the Open API community. Although the SID and the Open API are close cousins, there are differences between the models, for various reasons.
    In any case, for your use case, at Product Catalog level, you can do the following (all entity names as in Product Catalog API TMF620):
    • Define simple (atomic) Product Offerings for Voice, Data, and IR, each of these POs will contain exactly one parent Product Specification (again for Voice, Data, and IR), these PSs may have internal structure (composite PS) depending on your technical modeling needs.
    • Construct bundled (composite) Product Offerings for Business and Residential. Both these bundling POs will refer to the three atomic POs, but the Business PO will include the IR PO as mandatory, while the Residential PO will include it as Optional (using the BundledProductOfferingOption sub-resource to reflect this).
    I'm not sure how this relates to characteristics, but in any case if you need to restrict characteristic values from the PS in the context of a PO, you have the resource ProductSpecificationCharacteristicValueUse that allows you to do this.

    Hope it helps

    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.

  • 3.  RE: CustomerFacingServiceSpec Characteristic Queries

    TM Forum Member
    Posted Sep 07, 2020 01:33
    Hi @Jonathan Goldberg,

    We continued the discussion on the below post in Frameworx community:

    Basically the point is to allow flexibility to the user (CSR / Customer) to select whether do bar/un-bar the services during on-boarding, given that there is no impact on charges of the PO.

    Rabinder Devnani
    Sterlite Technologies Limited