Open APIs

 View Only
Expand all | Collapse all

TMF622 Product Order Item Action values

  • 1.  TMF622 Product Order Item Action values

    TM Forum Member
    Posted Nov 08, 2019 05:02
    Product Order Item has a field 'action' which is of enumeration type OrderItemActionType.
    This enumeration currently has following valid values:
    • add
    • modify   
    • delete
    • noChange
    This list should be extended to contain suspend (for temporary suspension of the service as per customer request or billing system) and resume.
    WDYT?



    ------------------------------
    Prashantkumar Sonawane
    Amdocs Management Limited
    ------------------------------


  • 2.  RE: TMF622 Product Order Item Action values

    TM Forum Member
    Posted Nov 09, 2019 13:59
    Amdocs experience from our existing ordering software implementations is indeed that the action types  include suspend and resume - @Ludovic Robert do you think we could open a CR for this to apply to the action enum for the various order (Product, Service, Resource)?​

    ------------------------------
    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: TMF622 Product Order Item Action values

    TM Forum Member
    Posted Nov 11, 2019 05:14
    Hello,

    It could be assessed. For me alternative is already existing: in a productOrder item you describe 'wished' product modification so in this case, suppose you have product #17 active. An order item on product = #17, with action = change and product.state = 'suspended' means that you request order to suspend this product. Exactly as you describe change product characteristic value. 
    Probably if required to have specific action in my implementation i will extend change enum value with change.changeState, change.changeCharateriscValue, etc...

    Hope it helps
    Ludovic​​

    ------------------------------
    Ludovic Robert
    Orange
    My answer are my own & don't represent necessarily my company or the TMF
    ------------------------------



  • 4.  RE: TMF622 Product Order Item Action values

    TM Forum Member
    Posted Nov 12, 2019 01:59
    Hi,

    Suspend & Resume are action performed as result of non-payment by the customer. Therefore the Account of the customer is suspended.
    What this means for the products of this customer is not always straightforward.
    Sometimes a product is completely switched of but in other cases a voice product is restricted to emergency services only, a TV product is limited to "free to air" content or an internet product is restricted to a customer support portal.

    It seems to me that with the product order you want to model exactly that change.
    In order to use a catalog driven approach a change action is most appropriate. It allows to model the required change in the catalog rather than reverting to special code for "suspension". Al attempts to use catalog driven orchestration are invain if you introduce new actions that can not easily be understood by a catalog.

    Hope this helps

    Koen Peeters
    Ciminko Luxemburg

    ------------------------------
    Koen Peeters
    Ciminko Luxembourg
    ------------------------------



  • 5.  RE: TMF622 Product Order Item Action values

    TM Forum Member
    Posted Nov 12, 2019 03:35
    Thanks Koen for your insights.
    Perhaps the most common reason for suspend (or resume) is due to collection (dunning) process. But other reasons for suspend/resume exist, including:
    • Customer request (she's going on holiday and wants to pay a reduced recurring charge during this period, in return for guarantee that the product will not be used)
    • Fraud (need to stop the service immediately to block continued fraudulent use while the fraud is being investigated)
    • More (perhaps) ...
    The motivation to have a specific action for suspend/resume at the order item level is to assist in choosing the relevant business process that executes the order delivery.

    In general, the allowed actions must be backed by the catalog, as you wrote. In the SID we have the ProductAction ABE, and this item is pointed to by both ProductSpecification and CustomerOrderItem. I think that we may be missing allowed actions in the API catalog (TMF620), I am considering opening a CR for this, irrespective of suspend/resume.

    ------------------------------
    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.
    ------------------------------



  • 6.  RE: TMF622 Product Order Item Action values

    TM Forum Member
    Posted Mar 01, 2021 00:47
    @Jonathan Goldberg  hi ,  I am trying to find the "Product Action ABE" in SID model , but no luck so far , can you help be guiding , where can I find it ? :)







    ------------------------------
    alok pradhan
    Netcracker Technology
    ------------------------------



  • 7.  RE: TMF622 Product Order Item Action values

    TM Forum Member
    Posted Nov 12, 2019 10:58
    Edited by Christopher Gonzalez Nov 12, 2019 10:58
    Hi I read all through your posts, and I want to add my experience to the group.

    When ever you are dealing with suspend/resume actions, those actions will impact a service, cause the product it is always supported by one or more services, so to me if you want to execute a suspend you need to do it over the services directly and not in the product level.

    My two cents...

    ------------------------------
    Christopher Gonzalez
    Intraway Corp
    ------------------------------



  • 8.  RE: TMF622 Product Order Item Action values

    TM Forum Member
    Posted Nov 12, 2019 13:31
    Hi Christopher
    The expectation is that the Product Order that executes a suspend will spawn the relevant service order(s) to execute the suspension on the network. But it must be done also at Product level since:
    • The recurring charge might be reduced (especially for a voluntary suspend), and this is done at BSS (Product Price) level
    • The end customer is generally unaware of Services, she will typically see Products in a customer-facing portal.
    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.
    ------------------------------



  • 9.  RE: TMF622 Product Order Item Action values

    TM Forum Member
    Posted Nov 12, 2019 16:35
    Thanks Jonathan, it really makes sense now that you are mentioning the customer portal and the possibility of a reduced price.

    ------------------------------
    Christopher Gonzalez
    Intraway Corp
    ------------------------------



  • 10.  RE: TMF622 Product Order Item Action values

    TM Forum Member
    Posted Jan 03, 2020 08:57
    Hi all,

    there was a similar discussion in at least one other post, see Re: Is it possible real-time unbarring process?

    * Let me point out that it is probably not sufficient from a business point of view to simply "suspend" or "resume" a product (respectively, the corresponding services). Instead, one might wish to suspend only specific parts of the product/service, e.g. for a telephony service only outgoing calls or international calls or similar.
    * Moreover, one might want to submit the reason and the originator for the suspension (e.g. customer wish or operator determined).
    * In addition, a suspension might imply a (near) real-time barring of the service, i.e. a direct (and synchronous) use of Service Configuration API (TMF 640) without instantiating a product order.

    Putting all together, I get the impression that a mere extension of the order item action type might serve as a quick and "technical" solution which, however, does not address thoroughly the complete business needs. Instead, my personal conclusion is to introduce a specific API for barring and unbarring purposes (with a suspension as a specific resource) instead of extending the TMF622 API. But of course, as always, there is more than one possible way to handle it...

    BR THomas

    ------------------------------
    Thomas Dupré
    Deutsche Telekom AG
    ------------------------------