Open APIs

 View Only

  • 1.  TMF641 Cancel Service Order - Assessing Cancellation

    Posted Mar 24, 2022 08:00
    Edited by Kanika Aggarwal Mar 24, 2022 08:00
    Hi,

    I would like to understand if there are any recommendation/best practices around assessing cancellation at SOM i.e. what validations should SOM implement to reject the request of cancelling service order. Some of the scenarios I am looking at are as below but will be more than happy to know about more such validations/scenarios.

    • Scenario 1: When service order comprising of more than one service order items is in progress and one of the order item is completed. Cancel service order request is received by SOM, should it still allow cancellation of the service order or reject the request because one of the order item is already completed?
      • If SOM rejects the cancellation in this scenario, how can we support in-flight cancellation of a service order which has order items, some of which completes in matter of seconds, while others are long running?
    • Scenario 2: When service order comprising of one service order item is in progress and service order item has action=add and service.state=active, should SOM allow cancellation for such service order i.e. should rollback be allowed when the intended target state is active?

    @Ludovic Robert tagging you here as I have seen your responses on a lot of threads around this topic and they have been very helpful :)

    Regards
    Kanika​

    ------------------------------
    Kanika Aggarwal
    VOCUS PTY LTD
    ------------------------------


  • 2.  RE: TMF641 Cancel Service Order - Assessing Cancellation

    Posted Mar 25, 2022 05:40
    Hello Kanika

    Not easy to answer you because not dependent of API capabilities but more on your implementation & SOM capabilities (in particular Service Order granularity)

    For me, I will look the situation from a service delivery perspective. You have to define  (design time) a service orchestration delivery for each one of your service, and  in this  delivery  process you identify the PONR.  Run time, when this PONR reach, cancel is impossible. When one item of the SO reach PONR, your SO cannot be cancelled.
    But this information should also use at POM level but , for me, PONR at service level did not mean automatically PONR at product order level. Indeed you can accept a PO cancel request and trigger new SO to get back your service in previous state.
    Bottom line: You have to take a look on the global orchestration Product/Service delivery; leverage PONR and probably keep in simple with limiting item volume in SO.

    Ludovic

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



  • 3.  RE: TMF641 Cancel Service Order - Assessing Cancellation

    Posted Apr 11, 2022 19:31
    Thanks Ludovic for getting back, appreciate that :)

    Very valid points and I think my takeaway from this is that:
    • SOM should allow for each service to define it's PONR
    • Product to service decomposition should also take into consideration how in-flight withdrawals will be supported among many other aspects
    Regards
    Kanika




    Original Message


Related Content