Open APIs

 View Only
  • 1.  TMF645_Service_Qualification_Management_API

    TM Forum Member
    Posted Sep 21, 2018 04:14
      |   view attached
    Hello,

    As described in the service qualification API, it must support the availability of service at a specified address. As our use case wants this API to support the availability of a service at only a single specified address in the customer order for us the relationship between service to place is one-to-one and not one-to-many.

    In this context I have few queries regarding the relationship between Service and Place [Geographical Address].   
    • Do we really need to maintain a one-to-many relationship between Service and Place ? This means we need to check within a serviceQualificationItem whether the service is available at multiple places. 
    • In this case where the relationship is one-to-many if service is available @ one place and not at the other, what will be the result of the serviceQualificationItem?
    Thanks and Regards,
    Shreyas Madwanna


    ------------------------------
    Shreyas Madwanna
    Tech Mahindra Limited
    TMForum Career Certified Professional
    ------------------------------


  • 2.  RE: TMF645_Service_Qualification_Management_API

    Posted Sep 24, 2018 05:16
    ​Hi Shreyas,
    Referring to your first question, I believe the list of Places related to a single serviceQualificationItem is needed in general to support services that in their nature connect (or must be necessarly available at) multiple locations e.g. E-LINE or E-LAN services. If the service as requested cannot be provided at any of the places in the list, I would expect the qualificationItemResult to be "unqualified" or "alternate". Of course, in your case you can include in the list only one item and use the API in a reduced manner.
    On the other hand, if the service is not necessarly requested at all places in the list, we can still use multiple serviceQualificationItem-s in the serviceQualification, each having its own result.

    On the second point, about how the unqualified result is reported when there are multiple places, we can note that the field eligibilityUnavailabilityReason is also a list. Using a list with the same number of items and same order of places,  we can specify a different reason for each place (for the qualified subset of places a special reason code would be required).

    Hope it helps.
    Best regards,

    ------------------------------
    Dino Pellegrini
    Solution Architect OSS Services&Network Management
    Ericsson Inc.
    ------------------------------



  • 3.  RE: TMF645_Service_Qualification_Management_API

    TM Forum Member
    Posted Oct 10, 2018 04:01
    Hello Dino,

    Thanks for you reply.

    1) We have modeled Place as a list although for our use case we are using only one place to identify the service availability
    2) For using multiple qualification reason can resolve this concern.

    Thanks & Regards,
    Shreyas Madwanna
    +32 465324190

    ------------------------------
    Shreyas Madwanna
    Tech Mahindra Limited
    TMForum Career Certified Professional
    ------------------------------