Open APIs

Hi Everyone,

Few Questions:

If we look at the Service State model given in the TMF641 document, it seems that the fulfillment work flow should not just be dependent on Order Item Action, rather it should also consider the Service State that is being requested in Service Order. 
So if the Order Item has action as Add and Service State is Designed, the fulfillment workflow should only execute the Design activities.
Similarly,  if the Order Item has action as Add and Service State is Active, the fulfillment workflow should only execute the Design, Reserve and Activation activities.
Is this understanding correct?

Another question: How Service Order Item States are related to Service States?
if in a particular Service Order, the Order Item has action as Add and Service State is Designed, the fulfillment workflow would execute the Design activities and Mark the Service Order Item as Completed?.
In such case, how the request would come to make the service active - new POST with Order Item action as Modify and Service State as Active?
OR
the 1st Order needs to be kept in IN PROGRESS state and the request to make service Active will come as PATCH?

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

Hello Prashantkumar 
For my perspective you got it.
The service order item describes a request to performean action to a service. The service state is part of this request.
the service order item state is use to track the action progress. There is in fact not really a hard link between service order item state and service state.

Regarding your second point.
You 'll have a POST serviceOrder
with an item with action add for a service to be in state designed.

Suppose everything goes well
The service order item state is completed
The service #48 in your inventory in designed state.
(if thing goes bad the service is not created and the service order is failed state)

Late you want to activate it.
So here you'll POST a service order (a new service order)
with an item with action change for  service #48 to be in state active.

Hope it helps
Ludovic


​​

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

Original Message:
Sent: May 05, 2020 23:14
From: Prashantkumar Sonawane
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi Everyone,

Few Questions:

If we look at the Service State model given in the TMF641 document, it seems that the fulfillment work flow should not just be dependent on Order Item Action, rather it should also consider the Service State that is being requested in Service Order.
So if the Order Item has action as Add and Service State is Designed, the fulfillment workflow should only execute the Design activities.
Similarly,  if the Order Item has action as Add and Service State is Active, the fulfillment workflow should only execute the Design, Reserve and Activation activities.
Is this understanding correct?

Another question: How Service Order Item States are related to Service States?
if in a particular Service Order, the Order Item has action as Add and Service State is Designed, the fulfillment workflow would execute the Design activities and Mark the Service Order Item as Completed?.
In such case, how the request would come to make the service active - new POST with Order Item action as Modify and Service State as Active?
OR
the 1st Order needs to be kept in IN PROGRESS state and the request to make service Active will come as PATCH?

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

Yes, It answers my question. Thanks!

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

Original Message:
Sent: May 06, 2020 02:24
From: Ludovic Robert
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hello Prashantkumar
For my perspective you got it.
The service order item describes a request to performean action to a service. The service state is part of this request.
the service order item state is use to track the action progress. There is in fact not really a hard link between service order item state and service state.

Regarding your second point.
You 'll have a POST serviceOrder
with an item with action add for a service to be in state designed.

Suppose everything goes well
The service order item state is completed
The service #48 in your inventory in designed state.
(if thing goes bad the service is not created and the service order is failed state)

Late you want to activate it.
So here you'll POST a service order (a new service order)
with an item with action change for  service #48 to be in state active.

Hope it helps
Ludovic


​​

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

Original Message:
Sent: May 05, 2020 23:14
From: Prashantkumar Sonawane
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi Everyone,

Few Questions:

If we look at the Service State model given in the TMF641 document, it seems that the fulfillment work flow should not just be dependent on Order Item Action, rather it should also consider the Service State that is being requested in Service Order.
So if the Order Item has action as Add and Service State is Designed, the fulfillment workflow should only execute the Design activities.
Similarly,  if the Order Item has action as Add and Service State is Active, the fulfillment workflow should only execute the Design, Reserve and Activation activities.
Is this understanding correct?

Another question: How Service Order Item States are related to Service States?
if in a particular Service Order, the Order Item has action as Add and Service State is Designed, the fulfillment workflow would execute the Design activities and Mark the Service Order Item as Completed?.
In such case, how the request would come to make the service active - new POST with Order Item action as Modify and Service State as Active?
OR
the 1st Order needs to be kept in IN PROGRESS state and the request to make service Active will come as PATCH?

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

Hi

If the Service state attribute in the service order is the requested end-state, how is the progress of the ordered service (e.g. designed->reserved->active) made available to the consumer?

Thanks in advance

------------------------------
Gary Wilson
Airbus
------------------------------

Original Message:
Sent: May 06, 2020 02:24
From: Ludovic Robert
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hello Prashantkumar 
For my perspective you got it.
The service order item describes a request to performean action to a service. The service state is part of this request.
the service order item state is use to track the action progress. There is in fact not really a hard link between service order item state and service state.

Regarding your second point.
You 'll have a POST serviceOrder
with an item with action add for a service to be in state designed.

Suppose everything goes well
The service order item state is completed
The service #48 in your inventory in designed state.
(if thing goes bad the service is not created and the service order is failed state)

Late you want to activate it.
So here you'll POST a service order (a new service order)
with an item with action change for  service #48 to be in state active.

Hope it helps
Ludovic


​​

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

Original Message:
Sent: May 05, 2020 23:14
From: Prashantkumar Sonawane
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi Everyone,

Few Questions:

If we look at the Service State model given in the TMF641 document, it seems that the fulfillment work flow should not just be dependent on Order Item Action, rather it should also consider the Service State that is being requested in Service Order.
So if the Order Item has action as Add and Service State is Designed, the fulfillment workflow should only execute the Design activities.
Similarly,  if the Order Item has action as Add and Service State is Active, the fulfillment workflow should only execute the Design, Reserve and Activation activities.
Is this understanding correct?

Another question: How Service Order Item States are related to Service States?
if in a particular Service Order, the Order Item has action as Add and Service State is Designed, the fulfillment workflow would execute the Design activities and Mark the Service Order Item as Completed?.
In such case, how the request would come to make the service active - new POST with Order Item action as Modify and Service State as Active?
OR
the 1st Order needs to be kept in IN PROGRESS state and the request to make service Active will come as PATCH?

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

Hi

I would suggest that this could be communicated by events relating to the state of the service order (ServiceOrderStateChange). Possibly you might want to go deeper, to the level of state on service order item.

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

Original Message:
Sent: Jul 10, 2024 10:57
From: Gary Wilson
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi

If the Service state attribute in the service order is the requested end-state, how is the progress of the ordered service (e.g. designed->reserved->active) made available to the consumer?

Thanks in advance

------------------------------
Gary Wilson
Airbus

Original Message:
Sent: May 06, 2020 02:24
From: Ludovic Robert
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hello Prashantkumar 
For my perspective you got it.
The service order item describes a request to performean action to a service. The service state is part of this request.
the service order item state is use to track the action progress. There is in fact not really a hard link between service order item state and service state.

Regarding your second point.
You 'll have a POST serviceOrder
with an item with action add for a service to be in state designed.

Suppose everything goes well
The service order item state is completed
The service #48 in your inventory in designed state.
(if thing goes bad the service is not created and the service order is failed state)

Late you want to activate it.
So here you'll POST a service order (a new service order)
with an item with action change for  service #48 to be in state active.

Hope it helps
Ludovic


​​

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

Original Message:
Sent: May 05, 2020 23:14
From: Prashantkumar Sonawane
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi Everyone,

Few Questions:

If we look at the Service State model given in the TMF641 document, it seems that the fulfillment work flow should not just be dependent on Order Item Action, rather it should also consider the Service State that is being requested in Service Order.
So if the Order Item has action as Add and Service State is Designed, the fulfillment workflow should only execute the Design activities.
Similarly,  if the Order Item has action as Add and Service State is Active, the fulfillment workflow should only execute the Design, Reserve and Activation activities.
Is this understanding correct?

Another question: How Service Order Item States are related to Service States?
if in a particular Service Order, the Order Item has action as Add and Service State is Designed, the fulfillment workflow would execute the Design activities and Mark the Service Order Item as Completed?.
In such case, how the request would come to make the service active - new POST with Order Item action as Modify and Service State as Active?
OR
the 1st Order needs to be kept in IN PROGRESS state and the request to make service Active will come as PATCH?

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

Have you considered using the serviceOrder.serviceOrderItem.state?

------------------------------
Dan d'Albuquerque
Individual
------------------------------

Original Message:
Sent: Jul 10, 2024 10:57
From: Gary Wilson
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi

If the Service state attribute in the service order is the requested end-state, how is the progress of the ordered service (e.g. designed->reserved->active) made available to the consumer?

Thanks in advance

------------------------------
Gary Wilson
Airbus

Original Message:
Sent: May 06, 2020 02:24
From: Ludovic Robert
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hello Prashantkumar 
For my perspective you got it.
The service order item describes a request to performean action to a service. The service state is part of this request.
the service order item state is use to track the action progress. There is in fact not really a hard link between service order item state and service state.

Regarding your second point.
You 'll have a POST serviceOrder
with an item with action add for a service to be in state designed.

Suppose everything goes well
The service order item state is completed
The service #48 in your inventory in designed state.
(if thing goes bad the service is not created and the service order is failed state)

Late you want to activate it.
So here you'll POST a service order (a new service order)
with an item with action change for  service #48 to be in state active.

Hope it helps
Ludovic


​​

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

Original Message:
Sent: May 05, 2020 23:14
From: Prashantkumar Sonawane
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi Everyone,

Few Questions:

If we look at the Service State model given in the TMF641 document, it seems that the fulfillment work flow should not just be dependent on Order Item Action, rather it should also consider the Service State that is being requested in Service Order.
So if the Order Item has action as Add and Service State is Designed, the fulfillment workflow should only execute the Design activities.
Similarly,  if the Order Item has action as Add and Service State is Active, the fulfillment workflow should only execute the Design, Reserve and Activation activities.
Is this understanding correct?

Another question: How Service Order Item States are related to Service States?
if in a particular Service Order, the Order Item has action as Add and Service State is Designed, the fulfillment workflow would execute the Design activities and Mark the Service Order Item as Completed?.
In such case, how the request would come to make the service active - new POST with Order Item action as Modify and Service State as Active?
OR
the 1st Order needs to be kept in IN PROGRESS state and the request to make service Active will come as PATCH?

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

Original Message:
Sent: 7/11/2024 5:58:00 AM
From: Dan d'Albuquerque
Subject: RE: TMF641: Order Item Action, Service State and Service Order Item State

Have you considered using the serviceOrder.serviceOrderItem.state?

------------------------------
Dan d'Albuquerque
Individual
------------------------------

Original Message:
Sent: Jul 10, 2024 10:57
From: Gary Wilson
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi

If the Service state attribute in the service order is the requested end-state, how is the progress of the ordered service (e.g. designed->reserved->active) made available to the consumer?

Thanks in advance

------------------------------
Gary Wilson
Airbus

Original Message:
Sent: May 06, 2020 02:24
From: Ludovic Robert
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hello Prashantkumar 
For my perspective you got it.
The service order item describes a request to performean action to a service. The service state is part of this request.
the service order item state is use to track the action progress. There is in fact not really a hard link between service order item state and service state.

Regarding your second point.
You 'll have a POST serviceOrder
with an item with action add for a service to be in state designed.

Suppose everything goes well
The service order item state is completed
The service #48 in your inventory in designed state.
(if thing goes bad the service is not created and the service order is failed state)

Late you want to activate it.
So here you'll POST a service order (a new service order)
with an item with action change for  service #48 to be in state active.

Hope it helps
Ludovic


​​

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

Original Message:
Sent: May 05, 2020 23:14
From: Prashantkumar Sonawane
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi Everyone,

Few Questions:

If we look at the Service State model given in the TMF641 document, it seems that the fulfillment work flow should not just be dependent on Order Item Action, rather it should also consider the Service State that is being requested in Service Order.
So if the Order Item has action as Add and Service State is Designed, the fulfillment workflow should only execute the Design activities.
Similarly,  if the Order Item has action as Add and Service State is Active, the fulfillment workflow should only execute the Design, Reserve and Activation activities.
Is this understanding correct?

Another question: How Service Order Item States are related to Service States?
if in a particular Service Order, the Order Item has action as Add and Service State is Designed, the fulfillment workflow would execute the Design activities and Mark the Service Order Item as Completed?.
In such case, how the request would come to make the service active - new POST with Order Item action as Modify and Service State as Active?
OR
the 1st Order needs to be kept in IN PROGRESS state and the request to make service Active will come as PATCH?

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

Are you not planning to maintain the service (instance) in the inventory?  In our implementation, the service.id is updated in the serviceOrder response and so we are able to query the service.state directly from the inventory, either using the TMF638 API or through the ServiceStateChangeEvent from Kafka.

------------------------------
Dan d'Albuquerque
Individual
------------------------------

Original Message:
Sent: Jul 11, 2024 06:24
From: Gary Wilson
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi Dan

My understanding is that the ServiceOrderItem state is to report/track the progress of the order item. Whereas the Service state is to report track the progress of the Service

The state values for both are completely different - so are not interchangeable. Also the ServiceOrder state is a consolidation of the (potentially) multiple ServiceOrderItem states

My understanding from the Forum discussion (and the definition of the Service state in v4 of the Service Order API) is that the ServiceRefOrValue state attribute can be used by the consumer to request that the OSS provide a Service to the end-state requested. This impacts the order processing - i.e. when the  order has been 'satisfied'. For example, if the requested Service defines a state = 'reserved', when the Service design has been completed, the ServiceOrderItem is 'Completed'

What we want to do is provide the consumer with the state of the Service they have ordered as it progresses - i.e. feasibilityChecked, designed, etc. Originally we had planned to use the ServiceRefORValue state attribute UNTIL we realised that this is the requested end-state and NOT for reporting/tracking the state of the requested service

Having discussed this internally, we think that the best approach is to retain the ServiceRefOrValue as a record of what was requested and a separate - but linked - Service entity to track the progress of the Service that has been ordered. Hopefully this is a common way of implementing it to support interoperability

Kind Regards

Gary Wilson

This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Airbus Defence and Space Limited disclaims any and all liability if this email transmission was virus corrupted, altered or falsified.
-o-
Emails to Airbus Defence and Space Limited may be processed, recorded and monitored outside the UK.
-o-
Airbus Defence and Space Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England

Original Message:
Sent: 7/11/2024 5:58:00 AM
From: Dan d'Albuquerque
Subject: RE: TMF641: Order Item Action, Service State and Service Order Item State

Have you considered using the serviceOrder.serviceOrderItem.state?

------------------------------
Dan d'Albuquerque
Individual

Original Message:
Sent: Jul 10, 2024 10:57
From: Gary Wilson
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi

If the Service state attribute in the service order is the requested end-state, how is the progress of the ordered service (e.g. designed->reserved->active) made available to the consumer?

Thanks in advance

------------------------------
Gary Wilson
Airbus

Original Message:
Sent: May 06, 2020 02:24
From: Ludovic Robert
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hello Prashantkumar 
For my perspective you got it.
The service order item describes a request to performean action to a service. The service state is part of this request.
the service order item state is use to track the action progress. There is in fact not really a hard link between service order item state and service state.

Regarding your second point.
You 'll have a POST serviceOrder
with an item with action add for a service to be in state designed.

Suppose everything goes well
The service order item state is completed
The service #48 in your inventory in designed state.
(if thing goes bad the service is not created and the service order is failed state)

Late you want to activate it.
So here you'll POST a service order (a new service order)
with an item with action change for  service #48 to be in state active.

Hope it helps
Ludovic


​​

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

Original Message:
Sent: May 05, 2020 23:14
From: Prashantkumar Sonawane
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi Everyone,

Few Questions:

If we look at the Service State model given in the TMF641 document, it seems that the fulfillment work flow should not just be dependent on Order Item Action, rather it should also consider the Service State that is being requested in Service Order.
So if the Order Item has action as Add and Service State is Designed, the fulfillment workflow should only execute the Design activities.
Similarly,  if the Order Item has action as Add and Service State is Active, the fulfillment workflow should only execute the Design, Reserve and Activation activities.
Is this understanding correct?

Another question: How Service Order Item States are related to Service States?
if in a particular Service Order, the Order Item has action as Add and Service State is Designed, the fulfillment workflow would execute the Design activities and Mark the Service Order Item as Completed?.
In such case, how the request would come to make the service active - new POST with Order Item action as Modify and Service State as Active?
OR
the 1st Order needs to be kept in IN PROGRESS state and the request to make service Active will come as PATCH?

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

Original Message:
Sent: 7/15/2024 9:54:00 PM
From: Dan d'Albuquerque
Subject: RE: TMF641: Order Item Action, Service State and Service Order Item State

Are you not planning to maintain the service (instance) in the inventory?  In our implementation, the service.id is updated in the serviceOrder response and so we are able to query the service.state directly from the inventory, either using the TMF638 API or through the ServiceStateChangeEvent from Kafka.

------------------------------
Dan d'Albuquerque
Individual
------------------------------

Original Message:
Sent: Jul 11, 2024 06:24
From: Gary Wilson
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi Dan

My understanding is that the ServiceOrderItem state is to report/track the progress of the order item. Whereas the Service state is to report track the progress of the Service

The state values for both are completely different - so are not interchangeable. Also the ServiceOrder state is a consolidation of the (potentially) multiple ServiceOrderItem states

My understanding from the Forum discussion (and the definition of the Service state in v4 of the Service Order API) is that the ServiceRefOrValue state attribute can be used by the consumer to request that the OSS provide a Service to the end-state requested. This impacts the order processing - i.e. when the  order has been 'satisfied'. For example, if the requested Service defines a state = 'reserved', when the Service design has been completed, the ServiceOrderItem is 'Completed'

What we want to do is provide the consumer with the state of the Service they have ordered as it progresses - i.e. feasibilityChecked, designed, etc. Originally we had planned to use the ServiceRefORValue state attribute UNTIL we realised that this is the requested end-state and NOT for reporting/tracking the state of the requested service

Having discussed this internally, we think that the best approach is to retain the ServiceRefOrValue as a record of what was requested and a separate - but linked - Service entity to track the progress of the Service that has been ordered. Hopefully this is a common way of implementing it to support interoperability

Kind Regards

Gary Wilson

This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Airbus Defence and Space Limited disclaims any and all liability if this email transmission was virus corrupted, altered or falsified.
-o-
Emails to Airbus Defence and Space Limited may be processed, recorded and monitored outside the UK.
-o-
Airbus Defence and Space Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England

Original Message:
Sent: 7/11/2024 5:58:00 AM
From: Dan d'Albuquerque
Subject: RE: TMF641: Order Item Action, Service State and Service Order Item State

Have you considered using the serviceOrder.serviceOrderItem.state?

------------------------------
Dan d'Albuquerque
Individual

Original Message:
Sent: Jul 10, 2024 10:57
From: Gary Wilson
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi

If the Service state attribute in the service order is the requested end-state, how is the progress of the ordered service (e.g. designed->reserved->active) made available to the consumer?

Thanks in advance

------------------------------
Gary Wilson
Airbus

Original Message:
Sent: May 06, 2020 02:24
From: Ludovic Robert
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hello Prashantkumar 
For my perspective you got it.
The service order item describes a request to performean action to a service. The service state is part of this request.
the service order item state is use to track the action progress. There is in fact not really a hard link between service order item state and service state.

Regarding your second point.
You 'll have a POST serviceOrder
with an item with action add for a service to be in state designed.

Suppose everything goes well
The service order item state is completed
The service #48 in your inventory in designed state.
(if thing goes bad the service is not created and the service order is failed state)

Late you want to activate it.
So here you'll POST a service order (a new service order)
with an item with action change for  service #48 to be in state active.

Hope it helps
Ludovic


​​

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

Original Message:
Sent: May 05, 2020 23:14
From: Prashantkumar Sonawane
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi Everyone,

Few Questions:

If we look at the Service State model given in the TMF641 document, it seems that the fulfillment work flow should not just be dependent on Order Item Action, rather it should also consider the Service State that is being requested in Service Order.
So if the Order Item has action as Add and Service State is Designed, the fulfillment workflow should only execute the Design activities.
Similarly,  if the Order Item has action as Add and Service State is Active, the fulfillment workflow should only execute the Design, Reserve and Activation activities.
Is this understanding correct?

Another question: How Service Order Item States are related to Service States?
if in a particular Service Order, the Order Item has action as Add and Service State is Designed, the fulfillment workflow would execute the Design activities and Mark the Service Order Item as Completed?.
In such case, how the request would come to make the service active - new POST with Order Item action as Modify and Service State as Active?
OR
the 1st Order needs to be kept in IN PROGRESS state and the request to make service Active will come as PATCH?

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

Hi

In this case, if the service is in designed state, how to cancel it ie free the resources such as unreserve a port as the service order is already completed ? Should we use 'delete' action in the POST request ? 

Thanks

Vidya

------------------------------
vidya sridharan
BT Group plc
------------------------------

Original Message:
Sent: May 06, 2020 02:24
From: Ludovic Robert
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hello Prashantkumar 
For my perspective you got it.
The service order item describes a request to performean action to a service. The service state is part of this request.
the service order item state is use to track the action progress. There is in fact not really a hard link between service order item state and service state.

Regarding your second point.
You 'll have a POST serviceOrder
with an item with action add for a service to be in state designed.

Suppose everything goes well
The service order item state is completed
The service #48 in your inventory in designed state.
(if thing goes bad the service is not created and the service order is failed state)

Late you want to activate it.
So here you'll POST a service order (a new service order)
with an item with action change for  service #48 to be in state active.

Hope it helps
Ludovic


​​

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

Original Message:
Sent: May 05, 2020 23:14
From: Prashantkumar Sonawane
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi Everyone,

Few Questions:

If we look at the Service State model given in the TMF641 document, it seems that the fulfillment work flow should not just be dependent on Order Item Action, rather it should also consider the Service State that is being requested in Service Order.
So if the Order Item has action as Add and Service State is Designed, the fulfillment workflow should only execute the Design activities.
Similarly,  if the Order Item has action as Add and Service State is Active, the fulfillment workflow should only execute the Design, Reserve and Activation activities.
Is this understanding correct?

Another question: How Service Order Item States are related to Service States?
if in a particular Service Order, the Order Item has action as Add and Service State is Designed, the fulfillment workflow would execute the Design activities and Mark the Service Order Item as Completed?.
In such case, how the request would come to make the service active - new POST with Order Item action as Modify and Service State as Active?
OR
the 1st Order needs to be kept in IN PROGRESS state and the request to make service Active will come as PATCH?

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

Yes, 

You submit new service order (POST request) with action=delete. The process flow should check that the service is designed, free the resources and set the service as terminated in the inventory.

------------------------------
Plamen Stanoev
Ericsson Inc.
------------------------------

Original Message:
Sent: Oct 30, 2025 13:56
From: vidya sridharan
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi

In this case, if the service is in designed state, how to cancel it ie free the resources such as unreserve a port as the service order is already completed ? Should we use 'delete' action in the POST request ? 

Thanks

Vidya

------------------------------
vidya sridharan
BT Group plc

Original Message:
Sent: May 06, 2020 02:24
From: Ludovic Robert
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hello Prashantkumar 
For my perspective you got it.
The service order item describes a request to performean action to a service. The service state is part of this request.
the service order item state is use to track the action progress. There is in fact not really a hard link between service order item state and service state.

Regarding your second point.
You 'll have a POST serviceOrder
with an item with action add for a service to be in state designed.

Suppose everything goes well
The service order item state is completed
The service #48 in your inventory in designed state.
(if thing goes bad the service is not created and the service order is failed state)

Late you want to activate it.
So here you'll POST a service order (a new service order)
with an item with action change for  service #48 to be in state active.

Hope it helps
Ludovic


​​

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

Original Message:
Sent: May 05, 2020 23:14
From: Prashantkumar Sonawane
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi Everyone,

Few Questions:

If we look at the Service State model given in the TMF641 document, it seems that the fulfillment work flow should not just be dependent on Order Item Action, rather it should also consider the Service State that is being requested in Service Order.
So if the Order Item has action as Add and Service State is Designed, the fulfillment workflow should only execute the Design activities.
Similarly,  if the Order Item has action as Add and Service State is Active, the fulfillment workflow should only execute the Design, Reserve and Activation activities.
Is this understanding correct?

Another question: How Service Order Item States are related to Service States?
if in a particular Service Order, the Order Item has action as Add and Service State is Designed, the fulfillment workflow would execute the Design activities and Mark the Service Order Item as Completed?.
In such case, how the request would come to make the service active - new POST with Order Item action as Modify and Service State as Active?
OR
the 1st Order needs to be kept in IN PROGRESS state and the request to make service Active will come as PATCH?

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

Thanks. Can we not use Service order state to manage the Service Order progression and get the calling system to send Patch request depending on the orchestration rules ? Support TMF641 POST is submitted with  ServiceOrderItem.action =Add and service state = active, domain service orchestrator progresses the service to a state beyond which it cannot progress due to external dependency ( in this cae action to be done by external system that submitted the post request). In this case, can we move the Service order. state to pending and notify the calling system. Then when the external dependency is cleared, calling system can PATCH the service order with state=inProgress and the Domain orchestrator will be able to progress the order to make the service active. In case again there is an orchestration dependency on external system, can we then move it to Pending ,this would mean a single service order can be used to make the service active with POST/PATCH operations.

Especially when the Domain Specific CFS decomposes to multiple RFS and each of the RFS progression depends on external system, then it adds complexity on Domain orchestrator to understand the actions to be taken on corresponding RFS on every POST operation.

So is it better option to use multiple POST to move the service from Initial state to Active or a single POST followed by PATCH to move the service from Initial state to Active ? What would be the recommendation/ better way to implement?

------------------------------
vidya sridharan
BT Group plc
------------------------------

Original Message:
Sent: Oct 30, 2025 17:39
From: Plamen Stanoev
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Yes, 

You submit new service order (POST request) with action=delete. The process flow should check that the service is designed, free the resources and set the service as terminated in the inventory.

------------------------------
Plamen Stanoev
Ericsson Inc.

Original Message:
Sent: Oct 30, 2025 13:56
From: vidya sridharan
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi

In this case, if the service is in designed state, how to cancel it ie free the resources such as unreserve a port as the service order is already completed ? Should we use 'delete' action in the POST request ? 

Thanks

Vidya

------------------------------
vidya sridharan
BT Group plc

Original Message:
Sent: May 06, 2020 02:24
From: Ludovic Robert
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hello Prashantkumar 
For my perspective you got it.
The service order item describes a request to performean action to a service. The service state is part of this request.
the service order item state is use to track the action progress. There is in fact not really a hard link between service order item state and service state.

Regarding your second point.
You 'll have a POST serviceOrder
with an item with action add for a service to be in state designed.

Suppose everything goes well
The service order item state is completed
The service #48 in your inventory in designed state.
(if thing goes bad the service is not created and the service order is failed state)

Late you want to activate it.
So here you'll POST a service order (a new service order)
with an item with action change for  service #48 to be in state active.

Hope it helps
Ludovic


​​

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

Original Message:
Sent: May 05, 2020 23:14
From: Prashantkumar Sonawane
Subject: TMF641: Order Item Action, Service State and Service Order Item State

Hi Everyone,

Few Questions:

If we look at the Service State model given in the TMF641 document, it seems that the fulfillment work flow should not just be dependent on Order Item Action, rather it should also consider the Service State that is being requested in Service Order.
So if the Order Item has action as Add and Service State is Designed, the fulfillment workflow should only execute the Design activities.
Similarly,  if the Order Item has action as Add and Service State is Active, the fulfillment workflow should only execute the Design, Reserve and Activation activities.
Is this understanding correct?

Another question: How Service Order Item States are related to Service States?
if in a particular Service Order, the Order Item has action as Add and Service State is Designed, the fulfillment workflow would execute the Design activities and Mark the Service Order Item as Completed?.
In such case, how the request would come to make the service active - new POST with Order Item action as Modify and Service State as Active?
OR
the 1st Order needs to be kept in IN PROGRESS state and the request to make service Active will come as PATCH?

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