Open APIs

 View Only
  • 1.  Missing API: Resource Qualification

    TM Forum Member
    Posted Sep 26, 2018 06:27
    I am under the impression that an additional API is required for Resource Qualification as part of the Pre-Order API.

    The scope of this API is the selection of an appropriate Resource for a new Order. 
    Some examples:
    • New Phone Numbers: During the sales process it must be possible to present the customer with a list of alternative numbers to choose from. The selection process  can give a different result depending on the address of the customer in order so that regulatory requirements of geographic numbering are fulfilled. The selection process for these number can also differ depending on certain characteristics like "Vanity" so that the customer can choose from a set of numbers that are considered "nicer" if he is willing to pay an extra fee for this. The presented numbers should be reserved in the inventory for the time required to create the order in order to prevent that the same number is proposed to multiple customers.
    • Ported Numbers: During the sales process it must be possible to validate if the number can be supported for a number portability process.
    • Quarantined Numbers: During the sales process it must be possible to validate that a particular customer can recover a number he previously owned for a new service.
    • High-end CPE: During the sales process it must be possible to validate if that CPE is available in stock or to report back expected delays in delivery due to ordering with a third party.
    • Fiber: report back on free fibers in a network cable and optionally reserve the fiber for a specific usage.



    ------------------------------
    Koenraad Peeters
    Ciminko Luxembourg
    ------------------------------


  • 2.  RE: Missing API: Resource Qualification

    TM Forum Member
    Posted Sep 27, 2018 03:58
    Hi
    Resource Inventory API should cover this, we are using a dedicated task for this. It is a combination of retrieve (GET logicalResource with filter) and changing the status of the retrieved (e.g. to Lock status).  This need was already discussed during the API spec. Also resource pool covering such use case but via pool request.

    ------------------------------
    Jacob Avraham
    Amdocs Management Limited
    ------------------------------



  • 3.  RE: Missing API: Resource Qualification

    TM Forum Member
    Posted Sep 29, 2018 06:25
    Hi Jacob,

    Although I understand that the Resource Inventory API contains some the building blocks required, we are missing something.

    ProductOffering Qualifications provides an API for proposing which ProductOfferings a customer can choose in a particular scenario. The Product Catalog already provides you API calls to find this out, by querying and filtering. Never the less a ProductOffering Qualification API was provided to handle that querying and filtering for you. The Product Offering Qualification implements the rules defined in the catalog to come to simple lists of alternatives that can shown to the customer. It also implements rules to filter based on a previous Service Qualification result and rules that limit migration paths (ex. upgrades allowed but downgrades not allowed). This results in an API that guides you through the "Offer selection" during the sales process in a consistent way.

    In a similar way a Resource Qualification API should provide the sales process a consistent flow through "Product Configuration" using not only the Resource Inventory but also the Product/Resource catalog to define how selection of appropriate resources is done.

    ------------------------------
    Koenraad Peeters
    Ciminko Luxembourg
    ------------------------------