Open APIs

Hi,

I would like to understand if there is any recommended mapping between product order and service order states in context of Cancel Order. 

When a cancel request is submitted for product, as per TMF622 lifecycle , it moves to assessingCancellation and POM is assessing if cancellation can be done or not. What happens to corresponding TMF641 service order which is inProgress.
Should POM move the service order to Pending state as soon as it get into assessingCancellation state? (this is based on fact that order.state is a patchable attribute in TMF641 v4.1)

Thanks
Kanika

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

Hello Kanika

We introduced Milestone at serviceOrder level (and we should have it also at productOrder level) and probably this is a good UC to leverage it. So for me, you receive a cancel ProductOrder :

1. PO shifts to assessingCancellation
2. POOM check ServiceOrder milestones
   1. If a Milestone indicates PONR (Point of no return) has been reached for the SO (or any SO Item) then I guess we should deny ProductOrder cancellation request
   2. if PONR not reached then POOM could trigger a CancelServiceOrder to the SOM. POOM will wait from SOM cancelServiceOrder outputs to modify PO state and provide an answer to Cancel ProductOrder request.

Hope it helps,
Ludovic

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

Original Message:
Sent: Mar 22, 2022 19:13
From: Kanika Aggarwal
Subject: Mapping between TMF622 and TMF641 for Cancel Order

Hi,

I would like to understand if there is any recommended mapping between product order and service order states in context of Cancel Order.

When a cancel request is submitted for product, as per TMF622 lifecycle , it moves to assessingCancellation and POM is assessing if cancellation can be done or not. What happens to corresponding TMF641 service order which is inProgress.
Should POM move the service order to Pending state as soon as it get into assessingCancellation state? (this is based on fact that order.state is a patchable attribute in TMF641 v4.1)

Thanks
Kanika

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

Original Message:
Sent: 3/23/2022 5:23:00 AM
From: Ludovic Robert
Subject: RE: Mapping between TMF622 and TMF641 for Cancel Order

Hello Kanika

We introduced Milestone at serviceOrder level (and we should have it also at productOrder level) and probably this is a good UC to leverage it. So for me, you receive a cancel ProductOrder :

1. PO shifts to assessingCancellation
2. POOM check ServiceOrder milestones
   1. If a Milestone indicates PONR (Point of no return) has been reached for the SO (or any SO Item) then I guess we should deny ProductOrder cancellation request
   2. if PONR not reached then POOM could trigger a CancelServiceOrder to the SOM. POOM will wait from SOM cancelServiceOrder outputs to modify PO state and provide an answer to Cancel ProductOrder request.

Hope it helps,
Ludovic

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

Original Message:
Sent: Mar 22, 2022 19:13
From: Kanika Aggarwal
Subject: Mapping between TMF622 and TMF641 for Cancel Order

Hi,

I would like to understand if there is any recommended mapping between product order and service order states in context of Cancel Order.

When a cancel request is submitted for product, as per TMF622 lifecycle , it moves to assessingCancellation and POM is assessing if cancellation can be done or not. What happens to corresponding TMF641 service order which is inProgress.
Should POM move the service order to Pending state as soon as it get into assessingCancellation state? (this is based on fact that order.state is a patchable attribute in TMF641 v4.1)

Thanks
Kanika

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

Kanika,
Look like a bit more complicated.... you want to hold the service order waiting to computing the cancellation request from a commercial perspective before to submit the technical cancel request (CancerServiceOrder) right?
If commercial did not allow the cancellation no impact on the service order.

I tend to think that this commercial assessment should very very short (in time) that you could serialize.
If it take time, yes probably you need to hold the service order.  Held status is at used when order cannot progressed due to an issue on provider side - this is not really the case here but probably you could introduce a substate like held.suspend status in your implem to requested a 'freeze' in your SOM for this SO. 

hope it helps

Ludovic

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

Original Message:
Sent: Mar 23, 2022 07:10
From: Kanika Aggarwal
Subject: Mapping between TMF622 and TMF641 for Cancel Order

Thanks Ludovic for getting back. Great suggestion on using Milestone as an indicator for POM to decide whether or not to submit cancellation for service order.

But while PO is in assessingCancellation state and POM is assessing cancellation in its own domain such as cost of cancellation etc. even before it requests cancellation to SOM, what should happen to the service order, should it keep progressing or should it be put into held/pending until POM completes it's assessment? 

Regards

Kanika

Original Message:
Sent: 3/23/2022 5:23:00 AM
From: Ludovic Robert
Subject: RE: Mapping between TMF622 and TMF641 for Cancel Order

Hello Kanika

We introduced Milestone at serviceOrder level (and we should have it also at productOrder level) and probably this is a good UC to leverage it. So for me, you receive a cancel ProductOrder :

1. PO shifts to assessingCancellation
2. POOM check ServiceOrder milestones
   1. If a Milestone indicates PONR (Point of no return) has been reached for the SO (or any SO Item) then I guess we should deny ProductOrder cancellation request
   2. if PONR not reached then POOM could trigger a CancelServiceOrder to the SOM. POOM will wait from SOM cancelServiceOrder outputs to modify PO state and provide an answer to Cancel ProductOrder request.

Hope it helps,
Ludovic

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

Original Message:
Sent: Mar 22, 2022 19:13
From: Kanika Aggarwal
Subject: Mapping between TMF622 and TMF641 for Cancel Order

Hi,

I would like to understand if there is any recommended mapping between product order and service order states in context of Cancel Order.

When a cancel request is submitted for product, as per TMF622 lifecycle , it moves to assessingCancellation and POM is assessing if cancellation can be done or not. What happens to corresponding TMF641 service order which is inProgress.
Should POM move the service order to Pending state as soon as it get into assessingCancellation state? (this is based on fact that order.state is a patchable attribute in TMF641 v4.1)

Thanks
Kanika

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

Original Message:
Sent: 3/23/2022 1:08:00 PM
From: Ludovic Robert
Subject: RE: Mapping between TMF622 and TMF641 for Cancel Order

Kanika,
Look like a bit more complicated.... you want to hold the service order waiting to computing the cancellation request from a commercial perspective before to submit the technical cancel request (CancerServiceOrder) right?
If commercial did not allow the cancellation no impact on the service order.

I tend to think that this commercial assessment should very very short (in time) that you could serialize.
If it take time, yes probably you need to hold the service order.  Held status is at used when order cannot progressed due to an issue on provider side - this is not really the case here but probably you could introduce a substate like held.suspend status in your implem to requested a 'freeze' in your SOM for this SO. 

hope it helps

Ludovic

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

Original Message:
Sent: Mar 23, 2022 07:10
From: Kanika Aggarwal
Subject: Mapping between TMF622 and TMF641 for Cancel Order

Thanks Ludovic for getting back. Great suggestion on using Milestone as an indicator for POM to decide whether or not to submit cancellation for service order.

But while PO is in assessingCancellation state and POM is assessing cancellation in its own domain such as cost of cancellation etc. even before it requests cancellation to SOM, what should happen to the service order, should it keep progressing or should it be put into held/pending until POM completes it's assessment? 

Regards

Kanika

Original Message:
Sent: 3/23/2022 5:23:00 AM
From: Ludovic Robert
Subject: RE: Mapping between TMF622 and TMF641 for Cancel Order

Hello Kanika

We introduced Milestone at serviceOrder level (and we should have it also at productOrder level) and probably this is a good UC to leverage it. So for me, you receive a cancel ProductOrder :

1. PO shifts to assessingCancellation
2. POOM check ServiceOrder milestones
   1. If a Milestone indicates PONR (Point of no return) has been reached for the SO (or any SO Item) then I guess we should deny ProductOrder cancellation request
   2. if PONR not reached then POOM could trigger a CancelServiceOrder to the SOM. POOM will wait from SOM cancelServiceOrder outputs to modify PO state and provide an answer to Cancel ProductOrder request.

Hope it helps,
Ludovic

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

Original Message:
Sent: Mar 22, 2022 19:13
From: Kanika Aggarwal
Subject: Mapping between TMF622 and TMF641 for Cancel Order

Hi,

I would like to understand if there is any recommended mapping between product order and service order states in context of Cancel Order.

When a cancel request is submitted for product, as per TMF622 lifecycle , it moves to assessingCancellation and POM is assessing if cancellation can be done or not. What happens to corresponding TMF641 service order which is inProgress.
Should POM move the service order to Pending state as soon as it get into assessingCancellation state? (this is based on fact that order.state is a patchable attribute in TMF641 v4.1)

Thanks
Kanika

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

Hello Kanika,

For me pending is when the delivery is stopped because we wait for something from the 'requester' side where Held is from the 'Provider' side so... yes you're right. From the SOM the requester is the POM and SOM must stop waiting from POM information. 

Ludovic

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

Original Message:
Sent: Mar 23, 2022 21:18
From: Kanika Aggarwal
Subject: Mapping between TMF622 and TMF641 for Cancel Order

Thanks Ludovic.

Yes it takes time to do commercial assessment sometimes. Would pending make more sense here? As per v4.1 documentation:

The Pending state is used when an order/item is currently in a waiting stage for an action/activity to be completed before the order/item can progress further, pending order amend or cancel assessment.

So while POM is in assessingCancellation state and doing commercial assessment, we should move the service order to pending state.

Regards

Kanika

Original Message:
Sent: 3/23/2022 1:08:00 PM
From: Ludovic Robert
Subject: RE: Mapping between TMF622 and TMF641 for Cancel Order

Kanika,
Look like a bit more complicated.... you want to hold the service order waiting to computing the cancellation request from a commercial perspective before to submit the technical cancel request (CancerServiceOrder) right?
If commercial did not allow the cancellation no impact on the service order.

I tend to think that this commercial assessment should very very short (in time) that you could serialize.
If it take time, yes probably you need to hold the service order.  Held status is at used when order cannot progressed due to an issue on provider side - this is not really the case here but probably you could introduce a substate like held.suspend status in your implem to requested a 'freeze' in your SOM for this SO.

hope it helps

Ludovic

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

Original Message:
Sent: Mar 23, 2022 07:10
From: Kanika Aggarwal
Subject: Mapping between TMF622 and TMF641 for Cancel Order

Thanks Ludovic for getting back. Great suggestion on using Milestone as an indicator for POM to decide whether or not to submit cancellation for service order.

But while PO is in assessingCancellation state and POM is assessing cancellation in its own domain such as cost of cancellation etc. even before it requests cancellation to SOM, what should happen to the service order, should it keep progressing or should it be put into held/pending until POM completes it's assessment? 

Regards

Kanika

Original Message:
Sent: 3/23/2022 5:23:00 AM
From: Ludovic Robert
Subject: RE: Mapping between TMF622 and TMF641 for Cancel Order

Hello Kanika

We introduced Milestone at serviceOrder level (and we should have it also at productOrder level) and probably this is a good UC to leverage it. So for me, you receive a cancel ProductOrder :

1. PO shifts to assessingCancellation
2. POOM check ServiceOrder milestones
   1. If a Milestone indicates PONR (Point of no return) has been reached for the SO (or any SO Item) then I guess we should deny ProductOrder cancellation request
   2. if PONR not reached then POOM could trigger a CancelServiceOrder to the SOM. POOM will wait from SOM cancelServiceOrder outputs to modify PO state and provide an answer to Cancel ProductOrder request.

Hope it helps,
Ludovic

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

Original Message:
Sent: Mar 22, 2022 19:13
From: Kanika Aggarwal
Subject: Mapping between TMF622 and TMF641 for Cancel Order

Hi,

I would like to understand if there is any recommended mapping between product order and service order states in context of Cancel Order.

When a cancel request is submitted for product, as per TMF622 lifecycle , it moves to assessingCancellation and POM is assessing if cancellation can be done or not. What happens to corresponding TMF641 service order which is inProgress.
Should POM move the service order to Pending state as soon as it get into assessingCancellation state? (this is based on fact that order.state is a patchable attribute in TMF641 v4.1)

Thanks
Kanika

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

Original Message:
Sent: 3/24/2022 3:59:00 AM
From: Ludovic Robert
Subject: RE: Mapping between TMF622 and TMF641 for Cancel Order

Hello Kanika,

For me pending is when the delivery is stopped because we wait for something from the 'requester' side where Held is from the 'Provider' side so... yes you're right. From the SOM the requester is the POM and SOM must stop waiting from POM information. 

Ludovic

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

Original Message:
Sent: Mar 23, 2022 21:18
From: Kanika Aggarwal
Subject: Mapping between TMF622 and TMF641 for Cancel Order

Thanks Ludovic.

Yes it takes time to do commercial assessment sometimes. Would pending make more sense here? As per v4.1 documentation:

The Pending state is used when an order/item is currently in a waiting stage for an action/activity to be completed before the order/item can progress further, pending order amend or cancel assessment.

So while POM is in assessingCancellation state and doing commercial assessment, we should move the service order to pending state.

Regards

Kanika

Original Message:
Sent: 3/23/2022 1:08:00 PM
From: Ludovic Robert
Subject: RE: Mapping between TMF622 and TMF641 for Cancel Order

Kanika,
Look like a bit more complicated.... you want to hold the service order waiting to computing the cancellation request from a commercial perspective before to submit the technical cancel request (CancerServiceOrder) right?
If commercial did not allow the cancellation no impact on the service order.

I tend to think that this commercial assessment should very very short (in time) that you could serialize.
If it take time, yes probably you need to hold the service order.  Held status is at used when order cannot progressed due to an issue on provider side - this is not really the case here but probably you could introduce a substate like held.suspend status in your implem to requested a 'freeze' in your SOM for this SO.

hope it helps

Ludovic

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

Original Message:
Sent: Mar 23, 2022 07:10
From: Kanika Aggarwal
Subject: Mapping between TMF622 and TMF641 for Cancel Order

Thanks Ludovic for getting back. Great suggestion on using Milestone as an indicator for POM to decide whether or not to submit cancellation for service order.

But while PO is in assessingCancellation state and POM is assessing cancellation in its own domain such as cost of cancellation etc. even before it requests cancellation to SOM, what should happen to the service order, should it keep progressing or should it be put into held/pending until POM completes it's assessment? 

Regards

Kanika

Original Message:
Sent: 3/23/2022 5:23:00 AM
From: Ludovic Robert
Subject: RE: Mapping between TMF622 and TMF641 for Cancel Order

Hello Kanika

We introduced Milestone at serviceOrder level (and we should have it also at productOrder level) and probably this is a good UC to leverage it. So for me, you receive a cancel ProductOrder :

1. PO shifts to assessingCancellation
2. POOM check ServiceOrder milestones
   1. If a Milestone indicates PONR (Point of no return) has been reached for the SO (or any SO Item) then I guess we should deny ProductOrder cancellation request
   2. if PONR not reached then POOM could trigger a CancelServiceOrder to the SOM. POOM will wait from SOM cancelServiceOrder outputs to modify PO state and provide an answer to Cancel ProductOrder request.

Hope it helps,
Ludovic

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

Original Message:
Sent: Mar 22, 2022 19:13
From: Kanika Aggarwal
Subject: Mapping between TMF622 and TMF641 for Cancel Order

Hi,

I would like to understand if there is any recommended mapping between product order and service order states in context of Cancel Order.

When a cancel request is submitted for product, as per TMF622 lifecycle , it moves to assessingCancellation and POM is assessing if cancellation can be done or not. What happens to corresponding TMF641 service order which is inProgress.
Should POM move the service order to Pending state as soon as it get into assessingCancellation state? (this is based on fact that order.state is a patchable attribute in TMF641 v4.1)

Thanks
Kanika

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