Open APIs

Here is a scenario where upstream OSS system can send two types of service order: 
1) fully automated - meaning, the request in itself has the complete information for fulfilling that service.
2) semi automated - upstream system request doesn't have all the information for completing the fulfillment of the order. Operational Users will login into order system, manually fill in additional  details on to the order form and then re-submit. Which then takes the same route as that of fully automated.

Is there any placeholder in TMF 641 service order API to capture this differentiation?

------------------------------
Aneesh Damodaran
BT Group plc
------------------------------

Hi Aneesh
Clarification questions - does the upstream (invoking) system "know" in advance that the order is incomplete? How does it know?
And what type of data is incomplete - would it be embedded characteristics and values, entire services, or what?
@Kamal Maghsoudlou, what do you think on this?

​

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

Usually, the submitting system treats an order as complete based on it's data model and definition of "Complete" vs "incomplete".
It submits the order with the Product and customer information and sometimes, additional enrichment is needed.
Ideal case:  The Order capture function has the necessary integration and enriches this data before submitting the Product Order.
However, considering the practicalities and state of legacy, this additional enrichment may need to be carried out during the Orchestration by the OM function.
Which API to use depends on the answer to "What is this additional enrichment?"
Is it results of L2 Site feasibility?
Is it additional data about the Network Access that the SOM needs?

Regards,
Jag

------------------------------
Jag Baddukonda
CSGI
------------------------------

Original Message:
Sent: Aug 03, 2021 06:32
From: Jonathan Goldberg
Subject: TMF641 Fully Automated vs Semi Automated Service Order

Hi Aneesh
Clarification questions - does the upstream (invoking) system "know" in advance that the order is incomplete? How does it know?
And what type of data is incomplete - would it be embedded characteristics and values, entire services, or what?
@Kamal Maghsoudlou, what do you think on this?

​

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

Hi Aneesh, B2C and B2B orders should be completed before sending to service order decomposition. B2C orders as fully completed during the capture while B2B normally requires the validation, enrichment, etc..., phases. All happening before sending the orders to provision. 
Could you please provide us with a bit more of information on your specific case?

------------------------------
Santiago Lorente
Salesforce
------------------------------

Hi All,

User in upstream system know in advance that a order for a specific product needs to be progressed as semi-automated. 

The team that submit the order from upstream want the Config engineers, a specialist team with access to a separate inventory systems, to validate the entries and add Access Circuit related information for a Layer3 VPN configuration. 

Hence the standard validations that we run on a fully automated order needs to be relaxed for semi-automated orders.  So I was looking for a placeholder in Service Order to differentiate the types order.

------------------------------
Aneesh Damodaran
BT Group plc
------------------------------

Original Message:
Sent: Aug 04, 2021 04:47
From: Santiago Lorente
Subject: TMF641 Fully Automated vs Semi Automated Service Order

Hi Aneesh, B2C and B2B orders should be completed before sending to service order decomposition. B2C orders as fully completed during the capture while B2B normally requires the validation, enrichment, etc..., phases. All happening before sending the orders to provision.
Could you please provide us with a bit more of information on your specific case?

------------------------------
Santiago Lorente
Salesforce
------------------------------

If it is L3 enrichment, then you can extend the 641 or 652 specs but cannot use those APIs as it is
641 and 652 are to trigger Service & Resource Provisioning after the L3 enrichment at the applicable CFS is completed, and not for Order enrichment of the Network last mile  Access details 
If it is L2 enrichment, then it is more of Work Order Management related and currently there is no API for Work Order like we have for Service Order and Resource Order management.

@Jonathan Goldberg , @Kamal Maghsoudlou , @David Milham: This is a case for new API for Work Order Management separated from Service and Resource Order Management

​

------------------------------
Jag Baddukonda
CSGI
------------------------------

Original Message:
Sent: Aug 04, 2021 12:16
From: Aneesh Damodaran
Subject: TMF641 Fully Automated vs Semi Automated Service Order

Hi All,

User in upstream system know in advance that a order for a specific product needs to be progressed as semi-automated.

The team that submit the order from upstream want the Config engineers, a specialist team with access to a separate inventory systems, to validate the entries and add Access Circuit related information for a Layer3 VPN configuration.

Hence the standard validations that we run on a fully automated order needs to be relaxed for semi-automated orders.  So I was looking for a placeholder in Service Order to differentiate the types order.

------------------------------
Aneesh Damodaran
BT Group plc
------------------------------


Original Message:
Sent: Aug 04, 2021 04:47
From: Santiago Lorente
Subject: TMF641 Fully Automated vs Semi Automated Service Order

Hi Aneesh, B2C and B2B orders should be completed before sending to service order decomposition. B2C orders as fully completed during the capture while B2B normally requires the validation, enrichment, etc..., phases. All happening before sending the orders to provision.
Could you please provide us with a bit more of information on your specific case?

------------------------------
Santiago Lorente
Salesforce

There's a Work Order API in development - so hopefully your point can be addressed there.

------------------------------
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: Aug 04, 2021 12:36
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF641 Fully Automated vs Semi Automated Service Order

If it is L3 enrichment, then you can extend the 641 or 652 specs but cannot use those APIs as it is
641 and 652 are to trigger Service & Resource Provisioning after the L3 enrichment at the applicable CFS is completed, and not for Order enrichment of the Network last mile  Access details
If it is L2 enrichment, then it is more of Work Order Management related and currently there is no API for Work Order like we have for Service Order and Resource Order management.

@Jonathan Goldberg , @Kamal Maghsoudlou , @David Milham: This is a case for new API for Work Order Management separated from Service and Resource Order Management

​

------------------------------
Jag Baddukonda
CSGI
------------------------------


Original Message:
Sent: Aug 04, 2021 12:16
From: Aneesh Damodaran
Subject: TMF641 Fully Automated vs Semi Automated Service Order

Hi All,

User in upstream system know in advance that a order for a specific product needs to be progressed as semi-automated.

The team that submit the order from upstream want the Config engineers, a specialist team with access to a separate inventory systems, to validate the entries and add Access Circuit related information for a Layer3 VPN configuration.

Hence the standard validations that we run on a fully automated order needs to be relaxed for semi-automated orders.  So I was looking for a placeholder in Service Order to differentiate the types order.

------------------------------
Aneesh Damodaran
BT Group plc


Original Message:
Sent: Aug 04, 2021 04:47
From: Santiago Lorente
Subject: TMF641 Fully Automated vs Semi Automated Service Order

Hi Aneesh, B2C and B2B orders should be completed before sending to service order decomposition. B2C orders as fully completed during the capture while B2B normally requires the validation, enrichment, etc..., phases. All happening before sending the orders to provision.
Could you please provide us with a bit more of information on your specific case?

------------------------------
Santiago Lorente
Salesforce

Got It. Thank you all for your valuable comments.

------------------------------
Aneesh Damodaran
BT Group plc
------------------------------

Original Message:
Sent: Aug 04, 2021 14:28
From: Jonathan Goldberg
Subject: TMF641 Fully Automated vs Semi Automated Service Order

There's a Work Order API in development - so hopefully your point can be addressed there.

------------------------------
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: Aug 04, 2021 12:36
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF641 Fully Automated vs Semi Automated Service Order

If it is L3 enrichment, then you can extend the 641 or 652 specs but cannot use those APIs as it is
641 and 652 are to trigger Service & Resource Provisioning after the L3 enrichment at the applicable CFS is completed, and not for Order enrichment of the Network last mile  Access details
If it is L2 enrichment, then it is more of Work Order Management related and currently there is no API for Work Order like we have for Service Order and Resource Order management.

@Jonathan Goldberg , @Kamal Maghsoudlou , @David Milham: This is a case for new API for Work Order Management separated from Service and Resource Order Management

​

------------------------------
Jag Baddukonda
CSGI


Original Message:
Sent: Aug 04, 2021 12:16
From: Aneesh Damodaran
Subject: TMF641 Fully Automated vs Semi Automated Service Order

Hi All,

User in upstream system know in advance that a order for a specific product needs to be progressed as semi-automated.

The team that submit the order from upstream want the Config engineers, a specialist team with access to a separate inventory systems, to validate the entries and add Access Circuit related information for a Layer3 VPN configuration.

Hence the standard validations that we run on a fully automated order needs to be relaxed for semi-automated orders.  So I was looking for a placeholder in Service Order to differentiate the types order.

------------------------------
Aneesh Damodaran
BT Group plc


Original Message:
Sent: Aug 04, 2021 04:47
From: Santiago Lorente
Subject: TMF641 Fully Automated vs Semi Automated Service Order

Hi Aneesh, B2C and B2B orders should be completed before sending to service order decomposition. B2C orders as fully completed during the capture while B2B normally requires the validation, enrichment, etc..., phases. All happening before sending the orders to provision.
Could you please provide us with a bit more of information on your specific case?

------------------------------
Santiago Lorente
Salesforce

Hi Jonathan,

Will it be possible for you to point me to the ongoing Work Order Management API work.​

------------------------------
Kinshuk Kulshreshtha
Oracle Corporation

My views posted on this forum are personal, and do not reflect the position of my employer or TM Forum.
------------------------------

Original Message:
Sent: Aug 04, 2021 14:28
From: Jonathan Goldberg
Subject: TMF641 Fully Automated vs Semi Automated Service Order

There's a Work Order API in development - so hopefully your point can be addressed there.

------------------------------
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: Aug 04, 2021 12:36
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF641 Fully Automated vs Semi Automated Service Order

If it is L3 enrichment, then you can extend the 641 or 652 specs but cannot use those APIs as it is
641 and 652 are to trigger Service & Resource Provisioning after the L3 enrichment at the applicable CFS is completed, and not for Order enrichment of the Network last mile  Access details
If it is L2 enrichment, then it is more of Work Order Management related and currently there is no API for Work Order like we have for Service Order and Resource Order management.

@Jonathan Goldberg , @Kamal Maghsoudlou , @David Milham: This is a case for new API for Work Order Management separated from Service and Resource Order Management

​

------------------------------
Jag Baddukonda
CSGI


Original Message:
Sent: Aug 04, 2021 12:16
From: Aneesh Damodaran
Subject: TMF641 Fully Automated vs Semi Automated Service Order

Hi All,

User in upstream system know in advance that a order for a specific product needs to be progressed as semi-automated.

The team that submit the order from upstream want the Config engineers, a specialist team with access to a separate inventory systems, to validate the entries and add Access Circuit related information for a Layer3 VPN configuration.

Hence the standard validations that we run on a fully automated order needs to be relaxed for semi-automated orders.  So I was looking for a placeholder in Service Order to differentiate the types order.

------------------------------
Aneesh Damodaran
BT Group plc


Original Message:
Sent: Aug 04, 2021 04:47
From: Santiago Lorente
Subject: TMF641 Fully Automated vs Semi Automated Service Order

Hi Aneesh, B2C and B2B orders should be completed before sending to service order decomposition. B2C orders as fully completed during the capture while B2B normally requires the validation, enrichment, etc..., phases. All happening before sending the orders to provision.
Could you please provide us with a bit more of information on your specific case?

------------------------------
Santiago Lorente
Salesforce

Kinshuk - if you feel that you will be able to contribute, the best procedure would be for you to join the Open API team and take part in the design and development process. But in any case, I'm sending your name to the lead for the Work Order API so that he'll be able to contact you via TMF community.

------------------------------
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: Aug 05, 2021 01:49
From: Kinshuk Kulshreshtha
Subject: TMF641 Fully Automated vs Semi Automated Service Order

Hi Jonathan,

Will it be possible for you to point me to the ongoing Work Order Management API work.​

------------------------------
Kinshuk Kulshreshtha
Oracle Corporation

My views posted on this forum are personal, and do not reflect the position of my employer or TM Forum.
------------------------------


Original Message:
Sent: Aug 04, 2021 14:28
From: Jonathan Goldberg
Subject: TMF641 Fully Automated vs Semi Automated Service Order

There's a Work Order API in development - so hopefully your point can be addressed there.

------------------------------
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: Aug 04, 2021 12:36
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF641 Fully Automated vs Semi Automated Service Order

If it is L3 enrichment, then you can extend the 641 or 652 specs but cannot use those APIs as it is
641 and 652 are to trigger Service & Resource Provisioning after the L3 enrichment at the applicable CFS is completed, and not for Order enrichment of the Network last mile  Access details
If it is L2 enrichment, then it is more of Work Order Management related and currently there is no API for Work Order like we have for Service Order and Resource Order management.

@Jonathan Goldberg , @Kamal Maghsoudlou , @David Milham: This is a case for new API for Work Order Management separated from Service and Resource Order Management

​

------------------------------
Jag Baddukonda
CSGI


Original Message:
Sent: Aug 04, 2021 12:16
From: Aneesh Damodaran
Subject: TMF641 Fully Automated vs Semi Automated Service Order

Hi All,

User in upstream system know in advance that a order for a specific product needs to be progressed as semi-automated.

The team that submit the order from upstream want the Config engineers, a specialist team with access to a separate inventory systems, to validate the entries and add Access Circuit related information for a Layer3 VPN configuration.

Hence the standard validations that we run on a fully automated order needs to be relaxed for semi-automated orders.  So I was looking for a placeholder in Service Order to differentiate the types order.

------------------------------
Aneesh Damodaran
BT Group plc


Original Message:
Sent: Aug 04, 2021 04:47
From: Santiago Lorente
Subject: TMF641 Fully Automated vs Semi Automated Service Order

Hi Aneesh, B2C and B2B orders should be completed before sending to service order decomposition. B2C orders as fully completed during the capture while B2B normally requires the validation, enrichment, etc..., phases. All happening before sending the orders to provision.
Could you please provide us with a bit more of information on your specific case?

------------------------------
Santiago Lorente
Salesforce

Hi,

A service order doesn't need to know before if it is going to be fully automated or semi automated. Any assumption that an external system makes about this can be wrong. A semi-automated flow can be fully automated at a later time. Automation typically goes in phases with the goal to improve the degree of automation. A fully automated can still get stuck on exceptional conditions (not enough bandwidth to fulfill request, no more IP addresses, VLANs or phone numbers matching the criteria).

The service order however has a way to indicate to the outside world that manual tasks are required. The lifecycleStatus "pending" actually indicates that the order is waiting for a manual intervention. By patching the lifecycleStatus to "inProgress", the task handling system can signal that the service order should retry to continue the process.

To understand which step needs to be tried to continue should be determined from the lifecycle of the service instead of the service order. "designed" will indicate that a CFS is succesfully decomposed in in RFS, but not all of the requiredResources have been allocated. "reserved" will indicate that all resources are allocated but not all of the supportingResources are operating.

Manual tasks in a server order usually evolve around resource allocation and getting resources operating.

I hope this clarifies how lifecycleStatus management is essential for fully or semi automated workflows.

Regards

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

Hi @Koen Peeters - thanks for providing this perspective. I will explore this option in detail to fix my current problem.​

------------------------------
Aneesh Damodaran
BT Group plc
------------------------------

Original Message:
Sent: Aug 05, 2021 05:33
From: Koen Peeters
Subject: TMF641 Fully Automated vs Semi Automated Service Order

Hi,

A service order doesn't need to know before if it is going to be fully automated or semi automated. Any assumption that an external system makes about this can be wrong. A semi-automated flow can be fully automated at a later time. Automation typically goes in phases with the goal to improve the degree of automation. A fully automated can still get stuck on exceptional conditions (not enough bandwidth to fulfill request, no more IP addresses, VLANs or phone numbers matching the criteria).

The service order however has a way to indicate to the outside world that manual tasks are required. The lifecycleStatus "pending" actually indicates that the order is waiting for a manual intervention. By patching the lifecycleStatus to "inProgress", the task handling system can signal that the service order should retry to continue the process.

To understand which step needs to be tried to continue should be determined from the lifecycle of the service instead of the service order. "designed" will indicate that a CFS is succesfully decomposed in in RFS, but not all of the requiredResources have been allocated. "reserved" will indicate that all resources are allocated but not all of the supportingResources are operating.

Manual tasks in a server order usually evolve around resource allocation and getting resources operating.

I hope this clarifies how lifecycleStatus management is essential for fully or semi automated workflows.

Regards

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