TM Forum Community

Hi folks

A while back, there was a discussion on introducing an ODA component for Service Orchestration and also Resource Orchestration/Provisioning.  I just looked at the latest IG1242 ODA Component Inventory document and there is nothing planned for those specific components as of yet.

Any idea whether these components are still in the pipeline, or have they been replaced by some other ODA-C producers of the TMF640/TMF702 OpenAPIs?

I can see that TAC-280 for introducing these new components is 'In progress' as of Nov/21.

Thanks

Hi folks

A while back, there was a discussion on introducing an ODA component for Service Orchestration and also Resource Orchestration/Provisioning.  I just looked at the latest IG1242 ODA Component Inventory document and there is nothing planned for those specific components as of yet.

Any idea whether these components are still in the pipeline, or have they been replaced by some other ODA-C producers of the TMF640/TMF702 OpenAPIs?

I can see that TAC-280 for introducing these new components is 'In progress' as of Nov/21.

Thanks

Hi Dan, we have already specified 2 components involved in delivery orchestration:

TMFC003 - Product Order Delivery Orchestration and Mgt (in charge of the orchestration of the delivery of Product Orders)

TMFC007 - Service Order Management (in charge of the orchestration of the delivery of CFS or Services)

And we are currently working on TMFC011 - Resource Order Management.

Hope you can find there what you are looking for.

Hi folks

A while back, there was a discussion on introducing an ODA component for Service Orchestration and also Resource Orchestration/Provisioning.  I just looked at the latest IG1242 ODA Component Inventory document and there is nothing planned for those specific components as of yet.

Any idea whether these components are still in the pipeline, or have they been replaced by some other ODA-C producers of the TMF640/TMF702 OpenAPIs?

I can see that TAC-280 for introducing these new components is 'In progress' as of Nov/21.

Thanks

Hi Sylvie

Thanks for your reply.

TMFC007 appears to address the SOM which exposes the TMF641 Service Ordering Management Open API.  I was wondering which ODA-C will expose the TMF640 Service Activation and Configuration API?  Various documentation suggests that TMF641 may be used for complex, asynchronous, orchestration; whereas TMF640 may be used for near  real-time activations and re-configurations within the network.

TAC-280 indicates the following Open API interactions between SOM/ROM/etc.

Hi Dan, we have already specified 2 components involved in delivery orchestration:

TMFC003 - Product Order Delivery Orchestration and Mgt (in charge of the orchestration of the delivery of Product Orders)

TMFC007 - Service Order Management (in charge of the orchestration of the delivery of CFS or Services)

And we are currently working on TMFC011 - Resource Order Management.

Hope you can find there what you are looking for.

Hi folks

A while back, there was a discussion on introducing an ODA component for Service Orchestration and also Resource Orchestration/Provisioning.  I just looked at the latest IG1242 ODA Component Inventory document and there is nothing planned for those specific components as of yet.

Any idea whether these components are still in the pipeline, or have they been replaced by some other ODA-C producers of the TMF640/TMF702 OpenAPIs?

I can see that TAC-280 for introducing these new components is 'In progress' as of Nov/21.

Thanks

There is also these two alternative  interaction diagram proposal

Production: Components & Interactions - Components and Canvas - TM Forum Confluence

I suspect this is an open issue with ODA C teams

Hi Sylvie

Thanks for your reply.

TMFC007 appears to address the SOM which exposes the TMF641 Service Ordering Management Open API.  I was wondering which ODA-C will expose the TMF640 Service Activation and Configuration API?  Various documentation suggests that TMF641 may be used for complex, asynchronous, orchestration; whereas TMF640 may be used for near  real-time activations and re-configurations within the network.

TAC-280 indicates the following Open API interactions between SOM/ROM/etc.

Hi Dan, we have already specified 2 components involved in delivery orchestration:

TMFC003 - Product Order Delivery Orchestration and Mgt (in charge of the orchestration of the delivery of Product Orders)

TMFC007 - Service Order Management (in charge of the orchestration of the delivery of CFS or Services)

And we are currently working on TMFC011 - Resource Order Management.

Hope you can find there what you are looking for.

Hi folks

A while back, there was a discussion on introducing an ODA component for Service Orchestration and also Resource Orchestration/Provisioning.  I just looked at the latest IG1242 ODA Component Inventory document and there is nothing planned for those specific components as of yet.

Any idea whether these components are still in the pipeline, or have they been replaced by some other ODA-C producers of the TMF640/TMF702 OpenAPIs?

I can see that TAC-280 for introducing these new components is 'In progress' as of Nov/21.

Thanks

Yes it is, and we plan to discuss it and publish Resource Order Mgt specification for sprint 5 (end mid october).

There is also these two alternative  interaction diagram proposal

Production: Components & Interactions - Components and Canvas - TM Forum Confluence

I suspect this is an open issue with ODA C teams

Hi Sylvie

Thanks for your reply.

TMFC007 appears to address the SOM which exposes the TMF641 Service Ordering Management Open API.  I was wondering which ODA-C will expose the TMF640 Service Activation and Configuration API?  Various documentation suggests that TMF641 may be used for complex, asynchronous, orchestration; whereas TMF640 may be used for near  real-time activations and re-configurations within the network.

TAC-280 indicates the following Open API interactions between SOM/ROM/etc.

Hi Dan, we have already specified 2 components involved in delivery orchestration:

TMFC003 - Product Order Delivery Orchestration and Mgt (in charge of the orchestration of the delivery of Product Orders)

TMFC007 - Service Order Management (in charge of the orchestration of the delivery of CFS or Services)

And we are currently working on TMFC011 - Resource Order Management.

Hope you can find there what you are looking for.

Hi folks

A while back, there was a discussion on introducing an ODA component for Service Orchestration and also Resource Orchestration/Provisioning.  I just looked at the latest IG1242 ODA Component Inventory document and there is nothing planned for those specific components as of yet.

Any idea whether these components are still in the pipeline, or have they been replaced by some other ODA-C producers of the TMF640/TMF702 OpenAPIs?

I can see that TAC-280 for introducing these new components is 'In progress' as of Nov/21.

Thanks

There is also these two alternative  interaction diagram proposal

Production: Components & Interactions - Components and Canvas - TM Forum Confluence

I suspect this is an open issue with ODA C teams

Hi Sylvie

Thanks for your reply.

TMFC007 appears to address the SOM which exposes the TMF641 Service Ordering Management Open API.  I was wondering which ODA-C will expose the TMF640 Service Activation and Configuration API?  Various documentation suggests that TMF641 may be used for complex, asynchronous, orchestration; whereas TMF640 may be used for near  real-time activations and re-configurations within the network.

TAC-280 indicates the following Open API interactions between SOM/ROM/etc.

Hi Dan, we have already specified 2 components involved in delivery orchestration:

TMFC003 - Product Order Delivery Orchestration and Mgt (in charge of the orchestration of the delivery of Product Orders)

TMFC007 - Service Order Management (in charge of the orchestration of the delivery of CFS or Services)

And we are currently working on TMFC011 - Resource Order Management.

Hope you can find there what you are looking for.

Hi folks

A while back, there was a discussion on introducing an ODA component for Service Orchestration and also Resource Orchestration/Provisioning.  I just looked at the latest IG1242 ODA Component Inventory document and there is nothing planned for those specific components as of yet.

Any idea whether these components are still in the pipeline, or have they been replaced by some other ODA-C producers of the TMF640/TMF702 OpenAPIs?

I can see that TAC-280 for introducing these new components is 'In progress' as of Nov/21.

Thanks

Hi Dave

I am having trouble following the link in your reply.  Any chance you could point me in the right direction?

Thanks!

There is also these two alternative  interaction diagram proposal

Production: Components & Interactions - Components and Canvas - TM Forum Confluence

I suspect this is an open issue with ODA C teams

Hi Sylvie

Thanks for your reply.

TMFC007 appears to address the SOM which exposes the TMF641 Service Ordering Management Open API.  I was wondering which ODA-C will expose the TMF640 Service Activation and Configuration API?  Various documentation suggests that TMF641 may be used for complex, asynchronous, orchestration; whereas TMF640 may be used for near  real-time activations and re-configurations within the network.

TAC-280 indicates the following Open API interactions between SOM/ROM/etc.

Hi Dan, we have already specified 2 components involved in delivery orchestration:

TMFC003 - Product Order Delivery Orchestration and Mgt (in charge of the orchestration of the delivery of Product Orders)

TMFC007 - Service Order Management (in charge of the orchestration of the delivery of CFS or Services)

And we are currently working on TMFC011 - Resource Order Management.

Hope you can find there what you are looking for.

Hi folks

A while back, there was a discussion on introducing an ODA component for Service Orchestration and also Resource Orchestration/Provisioning.  I just looked at the latest IG1242 ODA Component Inventory document and there is nothing planned for those specific components as of yet.

Any idea whether these components are still in the pipeline, or have they been replaced by some other ODA-C producers of the TMF640/TMF702 OpenAPIs?

I can see that TAC-280 for introducing these new components is 'In progress' as of Nov/21.

Thanks

Hi Dave

I am having trouble following the link in your reply.  Any chance you could point me in the right direction?

Thanks!

There is also these two alternative  interaction diagram proposal

Production: Components & Interactions - Components and Canvas - TM Forum Confluence

I suspect this is an open issue with ODA C teams

Hi Sylvie

Thanks for your reply.

TMFC007 appears to address the SOM which exposes the TMF641 Service Ordering Management Open API.  I was wondering which ODA-C will expose the TMF640 Service Activation and Configuration API?  Various documentation suggests that TMF641 may be used for complex, asynchronous, orchestration; whereas TMF640 may be used for near  real-time activations and re-configurations within the network.

TAC-280 indicates the following Open API interactions between SOM/ROM/etc.

Hi Dan, we have already specified 2 components involved in delivery orchestration:

TMFC003 - Product Order Delivery Orchestration and Mgt (in charge of the orchestration of the delivery of Product Orders)

TMFC007 - Service Order Management (in charge of the orchestration of the delivery of CFS or Services)

And we are currently working on TMFC011 - Resource Order Management.

Hope you can find there what you are looking for.

Hi folks

A while back, there was a discussion on introducing an ODA component for Service Orchestration and also Resource Orchestration/Provisioning.  I just looked at the latest IG1242 ODA Component Inventory document and there is nothing planned for those specific components as of yet.

Any idea whether these components are still in the pipeline, or have they been replaced by some other ODA-C producers of the TMF640/TMF702 OpenAPIs?

I can see that TAC-280 for introducing these new components is 'In progress' as of Nov/21.

Thanks