Open APIs

​Hi all,
I would like to ask if using TMF 622 is it possible to manage blended orders (e.g. Device + accessories)? If yes, what are the parameters that I should consider?
Thanks in advance,
Filippo

------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION
------------------------------

Hi Filippo
Typically a Product Order for new products is instantiated from one (or perhaps more than one) Product Offering. So if you had an offering that bundled device with accessories, your order would contain products derived from the bundling offering, the device and the accessories. But you can also create an order based on multiple offerings. It's entirely up to the way you want to manage your business.
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.
------------------------------

Hi Jonathan,
first of all thanks for your reply. In accordance with your reply, this mean that I should consider the resource"productRelationship "?
Thanks in advance for the reply,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION
------------------------------

Original Message:
Sent: Oct 17, 2021 05:14
From: Jonathan Goldberg
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo
Typically a Product Order for new products is instantiated from one (or perhaps more than one) Product Offering. So if you had an offering that bundled device with accessories, your order would contain products derived from the bundling offering, the device and the accessories. But you can also create an order based on multiple offerings. It's entirely up to the way you want to manage your business.
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.
------------------------------

Hi Filippo,
While creating the Product Offering, you must define the entire structure i.e. PO, PS, RS, CFS (and RFS). The PO622 will consider the PO and the child POs with the related PS for each of the POs. 
It is up to you to model the device as a child PO or directly as a PS with RS under the Bundle PO. But once this is done, this structure is instantiated in the PO622.

Regards,
Jag

------------------------------
Jag Baddukonda
CSG
------------------------------

Original Message:
Sent: Oct 18, 2021 04:08
From: Filippo Roberto Valeriani
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Jonathan,
first of all thanks for your reply. In accordance with your reply, this mean that I should consider the resource"productRelationship "?
Thanks in advance for the reply,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION
------------------------------


Original Message:
Sent: Oct 17, 2021 05:14
From: Jonathan Goldberg
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo
Typically a Product Order for new products is instantiated from one (or perhaps more than one) Product Offering. So if you had an offering that bundled device with accessories, your order would contain products derived from the bundling offering, the device and the accessories. But you can also create an order based on multiple offerings. It's entirely up to the way you want to manage your business.
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.

Hi Jag,
thanks for your reply. I catch your point. The only part that I miss is this one "directly as a PS with RS under the Bundle PO". What do you mean?
Thanks in advance,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION
------------------------------

Original Message:
Sent: Oct 18, 2021 08:30
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo,
While creating the Product Offering, you must define the entire structure i.e. PO, PS, RS, CFS (and RFS). The PO622 will consider the PO and the child POs with the related PS for each of the POs.
It is up to you to model the device as a child PO or directly as a PS with RS under the Bundle PO. But once this is done, this structure is instantiated in the PO622.

Regards,
Jag

------------------------------
Jag Baddukonda
CSG
------------------------------


Original Message:
Sent: Oct 18, 2021 04:08
From: Filippo Roberto Valeriani
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Jonathan,
first of all thanks for your reply. In accordance with your reply, this mean that I should consider the resource"productRelationship "?
Thanks in advance for the reply,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION


Original Message:
Sent: Oct 17, 2021 05:14
From: Jonathan Goldberg
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo
Typically a Product Order for new products is instantiated from one (or perhaps more than one) Product Offering. So if you had an offering that bundled device with accessories, your order would contain products derived from the bundling offering, the device and the accessories. But you can also create an order based on multiple offerings. It's entirely up to the way you want to manage your business.
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.

It is upto how you model the structure.
The Device can be a separate PO with PS and RS or you need not model a Child PO and directly have the PS under the Bundle PO (is the device always valid irrespective of the cardinality and the configuration)

------------------------------
Jag Baddukonda
CSG
------------------------------

Original Message:
Sent: Oct 19, 2021 04:30
From: Filippo Roberto Valeriani
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Jag,
thanks for your reply. I catch your point. The only part that I miss is this one "directly as a PS with RS under the Bundle PO". What do you mean?
Thanks in advance,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION
------------------------------


Original Message:
Sent: Oct 18, 2021 08:30
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo,
While creating the Product Offering, you must define the entire structure i.e. PO, PS, RS, CFS (and RFS). The PO622 will consider the PO and the child POs with the related PS for each of the POs.
It is up to you to model the device as a child PO or directly as a PS with RS under the Bundle PO. But once this is done, this structure is instantiated in the PO622.

Regards,
Jag

------------------------------
Jag Baddukonda
CSG


Original Message:
Sent: Oct 18, 2021 04:08
From: Filippo Roberto Valeriani
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Jonathan,
first of all thanks for your reply. In accordance with your reply, this mean that I should consider the resource"productRelationship "?
Thanks in advance for the reply,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION


Original Message:
Sent: Oct 17, 2021 05:14
From: Jonathan Goldberg
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo
Typically a Product Order for new products is instantiated from one (or perhaps more than one) Product Offering. So if you had an offering that bundled device with accessories, your order would contain products derived from the bundling offering, the device and the accessories. But you can also create an order based on multiple offerings. It's entirely up to the way you want to manage your business.
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.

You might like to look at the best practice for CPE and accessories documented in:  

IG1236 Best Practice CPE Modelling for Quotation, Ordering, Delivery and Support v1.0.0

@Greg Herringer  was the author and can handle any questions.

​

------------------------------
Dave Milham
TM Forum, Chief Architect
------------------------------

Original Message:
Sent: Oct 19, 2021 07:36
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF622 Product Ordering API REST Specification - Blended order management

It is upto how you model the structure.
The Device can be a separate PO with PS and RS or you need not model a Child PO and directly have the PS under the Bundle PO (is the device always valid irrespective of the cardinality and the configuration)

------------------------------
Jag Baddukonda
CSG
------------------------------


Original Message:
Sent: Oct 19, 2021 04:30
From: Filippo Roberto Valeriani
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Jag,
thanks for your reply. I catch your point. The only part that I miss is this one "directly as a PS with RS under the Bundle PO". What do you mean?
Thanks in advance,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION


Original Message:
Sent: Oct 18, 2021 08:30
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo,
While creating the Product Offering, you must define the entire structure i.e. PO, PS, RS, CFS (and RFS). The PO622 will consider the PO and the child POs with the related PS for each of the POs.
It is up to you to model the device as a child PO or directly as a PS with RS under the Bundle PO. But once this is done, this structure is instantiated in the PO622.

Regards,
Jag

------------------------------
Jag Baddukonda
CSG


Original Message:
Sent: Oct 18, 2021 04:08
From: Filippo Roberto Valeriani
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Jonathan,
first of all thanks for your reply. In accordance with your reply, this mean that I should consider the resource"productRelationship "?
Thanks in advance for the reply,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION


Original Message:
Sent: Oct 17, 2021 05:14
From: Jonathan Goldberg
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo
Typically a Product Order for new products is instantiated from one (or perhaps more than one) Product Offering. So if you had an offering that bundled device with accessories, your order would contain products derived from the bundling offering, the device and the accessories. But you can also create an order based on multiple offerings. It's entirely up to the way you want to manage your business.
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.

Thanks for the shout out @David Milham and yes I would be happy to answer specific questions based on the document and the original question about handling product orders with a variety of product specifications.  The other responses in this thread give great advice - it comes down to the structure of the Product Offerings and the underlying Product Specifications. ​

------------------------------
Greg Herringer
IBM Corporation
------------------------------

Original Message:
Sent: Oct 20, 2021 03:59
From: Dave Milham
Subject: TMF622 Product Ordering API REST Specification - Blended order management

You might like to look at the best practice for CPE and accessories documented in:  

IG1236 Best Practice CPE Modelling for Quotation, Ordering, Delivery and Support v1.0.0

@Greg Herringer  was the author and can handle any questions.

​

------------------------------
Dave Milham
TM Forum, Chief Architect
------------------------------


Original Message:
Sent: Oct 19, 2021 07:36
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF622 Product Ordering API REST Specification - Blended order management

It is upto how you model the structure.
The Device can be a separate PO with PS and RS or you need not model a Child PO and directly have the PS under the Bundle PO (is the device always valid irrespective of the cardinality and the configuration)

------------------------------
Jag Baddukonda
CSG


Original Message:
Sent: Oct 19, 2021 04:30
From: Filippo Roberto Valeriani
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Jag,
thanks for your reply. I catch your point. The only part that I miss is this one "directly as a PS with RS under the Bundle PO". What do you mean?
Thanks in advance,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION


Original Message:
Sent: Oct 18, 2021 08:30
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo,
While creating the Product Offering, you must define the entire structure i.e. PO, PS, RS, CFS (and RFS). The PO622 will consider the PO and the child POs with the related PS for each of the POs.
It is up to you to model the device as a child PO or directly as a PS with RS under the Bundle PO. But once this is done, this structure is instantiated in the PO622.

Regards,
Jag

------------------------------
Jag Baddukonda
CSG


Original Message:
Sent: Oct 18, 2021 04:08
From: Filippo Roberto Valeriani
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Jonathan,
first of all thanks for your reply. In accordance with your reply, this mean that I should consider the resource"productRelationship "?
Thanks in advance for the reply,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION


Original Message:
Sent: Oct 17, 2021 05:14
From: Jonathan Goldberg
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo
Typically a Product Order for new products is instantiated from one (or perhaps more than one) Product Offering. So if you had an offering that bundled device with accessories, your order would contain products derived from the bundling offering, the device and the accessories. But you can also create an order based on multiple offerings. It's entirely up to the way you want to manage your business.
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.

I forgot we also have the guide on the Product Offering Product Spec considerations in 

IG1233 Product & Service Modelling Best Practices – Conforming to ODA v2.0.0

------------------------------
Dave Milham
TM Forum, Chief Architect
------------------------------

Original Message:
Sent: Oct 20, 2021 12:26
From: Greg Herringer
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Thanks for the shout out @David Milham and yes I would be happy to answer specific questions based on the document and the original question about handling product orders with a variety of product specifications.  The other responses in this thread give great advice - it comes down to the structure of the Product Offerings and the underlying Product Specifications. ​

------------------------------
Greg Herringer
IBM Corporation
------------------------------


Original Message:
Sent: Oct 20, 2021 03:59
From: Dave Milham
Subject: TMF622 Product Ordering API REST Specification - Blended order management

You might like to look at the best practice for CPE and accessories documented in:  

IG1236 Best Practice CPE Modelling for Quotation, Ordering, Delivery and Support v1.0.0

@Greg Herringer  was the author and can handle any questions.

​

------------------------------
Dave Milham
TM Forum, Chief Architect


Original Message:
Sent: Oct 19, 2021 07:36
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF622 Product Ordering API REST Specification - Blended order management

It is upto how you model the structure.
The Device can be a separate PO with PS and RS or you need not model a Child PO and directly have the PS under the Bundle PO (is the device always valid irrespective of the cardinality and the configuration)

------------------------------
Jag Baddukonda
CSG


Original Message:
Sent: Oct 19, 2021 04:30
From: Filippo Roberto Valeriani
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Jag,
thanks for your reply. I catch your point. The only part that I miss is this one "directly as a PS with RS under the Bundle PO". What do you mean?
Thanks in advance,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION


Original Message:
Sent: Oct 18, 2021 08:30
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo,
While creating the Product Offering, you must define the entire structure i.e. PO, PS, RS, CFS (and RFS). The PO622 will consider the PO and the child POs with the related PS for each of the POs.
It is up to you to model the device as a child PO or directly as a PS with RS under the Bundle PO. But once this is done, this structure is instantiated in the PO622.

Regards,
Jag

------------------------------
Jag Baddukonda
CSG


Original Message:
Sent: Oct 18, 2021 04:08
From: Filippo Roberto Valeriani
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Jonathan,
first of all thanks for your reply. In accordance with your reply, this mean that I should consider the resource"productRelationship "?
Thanks in advance for the reply,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION


Original Message:
Sent: Oct 17, 2021 05:14
From: Jonathan Goldberg
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo
Typically a Product Order for new products is instantiated from one (or perhaps more than one) Product Offering. So if you had an offering that bundled device with accessories, your order would contain products derived from the bundling offering, the device and the accessories. But you can also create an order based on multiple offerings. It's entirely up to the way you want to manage your business.
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.

Specifically with regard to Filippo's original query and some of the answers here:

• It's not a given that every Product Spec will have Resource Spec (CFS). Accessories (headsets, batteries, and so forth) would probably not need corresponding resources.
• Modeling accessories as separate, independent product specs and offerings means that you can be more flexible about pricing and supply (e.g. supply device without accessory). Embedding an accessory product spec as a child of a device product spec means essentially that any offerings based on this will sell the device and the accessory.
  

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: Oct 20, 2021 12:35
From: Dave Milham
Subject: TMF622 Product Ordering API REST Specification - Blended order management

I forgot we also have the guide on the Product Offering Product Spec considerations in

IG1233 Product & Service Modelling Best Practices – Conforming to ODA v2.0.0

------------------------------
Dave Milham
TM Forum, Chief Architect
------------------------------


Original Message:
Sent: Oct 20, 2021 12:26
From: Greg Herringer
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Thanks for the shout out @David Milham and yes I would be happy to answer specific questions based on the document and the original question about handling product orders with a variety of product specifications.  The other responses in this thread give great advice - it comes down to the structure of the Product Offerings and the underlying Product Specifications. ​

------------------------------
Greg Herringer
IBM Corporation


Original Message:
Sent: Oct 20, 2021 03:59
From: Dave Milham
Subject: TMF622 Product Ordering API REST Specification - Blended order management

You might like to look at the best practice for CPE and accessories documented in:  

IG1236 Best Practice CPE Modelling for Quotation, Ordering, Delivery and Support v1.0.0

@Greg Herringer  was the author and can handle any questions.

​

------------------------------
Dave Milham
TM Forum, Chief Architect


Original Message:
Sent: Oct 19, 2021 07:36
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF622 Product Ordering API REST Specification - Blended order management

It is upto how you model the structure.
The Device can be a separate PO with PS and RS or you need not model a Child PO and directly have the PS under the Bundle PO (is the device always valid irrespective of the cardinality and the configuration)

------------------------------
Jag Baddukonda
CSG


Original Message:
Sent: Oct 19, 2021 04:30
From: Filippo Roberto Valeriani
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Jag,
thanks for your reply. I catch your point. The only part that I miss is this one "directly as a PS with RS under the Bundle PO". What do you mean?
Thanks in advance,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION


Original Message:
Sent: Oct 18, 2021 08:30
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo,
While creating the Product Offering, you must define the entire structure i.e. PO, PS, RS, CFS (and RFS). The PO622 will consider the PO and the child POs with the related PS for each of the POs.
It is up to you to model the device as a child PO or directly as a PS with RS under the Bundle PO. But once this is done, this structure is instantiated in the PO622.

Regards,
Jag

------------------------------
Jag Baddukonda
CSG


Original Message:
Sent: Oct 18, 2021 04:08
From: Filippo Roberto Valeriani
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Jonathan,
first of all thanks for your reply. In accordance with your reply, this mean that I should consider the resource"productRelationship "?
Thanks in advance for the reply,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION


Original Message:
Sent: Oct 17, 2021 05:14
From: Jonathan Goldberg
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo
Typically a Product Order for new products is instantiated from one (or perhaps more than one) Product Offering. So if you had an offering that bundled device with accessories, your order would contain products derived from the bundling offering, the device and the accessories. But you can also create an order based on multiple offerings. It's entirely up to the way you want to manage your business.
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.

On the accessory topic we have another guide 

IG1236 Best Practice CPE Modelling for Quotation, Ordering, Delivery and Support v1.0.0

------------------------------
Dave Milham
TM Forum, Chief Architect
------------------------------

Original Message:
Sent: Oct 25, 2021 05:56
From: Jonathan Goldberg
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Specifically with regard to Filippo's original query and some of the answers here:

• It's not a given that every Product Spec will have Resource Spec (CFS). Accessories (headsets, batteries, and so forth) would probably not need corresponding resources.
• Modeling accessories as separate, independent product specs and offerings means that you can be more flexible about pricing and supply (e.g. supply device without accessory). Embedding an accessory product spec as a child of a device product spec means essentially that any offerings based on this will sell the device and the accessory.
  

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: Oct 20, 2021 12:35
From: Dave Milham
Subject: TMF622 Product Ordering API REST Specification - Blended order management

I forgot we also have the guide on the Product Offering Product Spec considerations in

IG1233 Product & Service Modelling Best Practices – Conforming to ODA v2.0.0

------------------------------
Dave Milham
TM Forum, Chief Architect


Original Message:
Sent: Oct 20, 2021 12:26
From: Greg Herringer
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Thanks for the shout out @David Milham and yes I would be happy to answer specific questions based on the document and the original question about handling product orders with a variety of product specifications.  The other responses in this thread give great advice - it comes down to the structure of the Product Offerings and the underlying Product Specifications. ​

------------------------------
Greg Herringer
IBM Corporation


Original Message:
Sent: Oct 20, 2021 03:59
From: Dave Milham
Subject: TMF622 Product Ordering API REST Specification - Blended order management

You might like to look at the best practice for CPE and accessories documented in:  

IG1236 Best Practice CPE Modelling for Quotation, Ordering, Delivery and Support v1.0.0

@Greg Herringer  was the author and can handle any questions.

​

------------------------------
Dave Milham
TM Forum, Chief Architect


Original Message:
Sent: Oct 19, 2021 07:36
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF622 Product Ordering API REST Specification - Blended order management

It is upto how you model the structure.
The Device can be a separate PO with PS and RS or you need not model a Child PO and directly have the PS under the Bundle PO (is the device always valid irrespective of the cardinality and the configuration)

------------------------------
Jag Baddukonda
CSG


Original Message:
Sent: Oct 19, 2021 04:30
From: Filippo Roberto Valeriani
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Jag,
thanks for your reply. I catch your point. The only part that I miss is this one "directly as a PS with RS under the Bundle PO". What do you mean?
Thanks in advance,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION


Original Message:
Sent: Oct 18, 2021 08:30
From: Sri Jagadish (Jag) Baddukonda
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo,
While creating the Product Offering, you must define the entire structure i.e. PO, PS, RS, CFS (and RFS). The PO622 will consider the PO and the child POs with the related PS for each of the POs.
It is up to you to model the device as a child PO or directly as a PS with RS under the Bundle PO. But once this is done, this structure is instantiated in the PO622.

Regards,
Jag

------------------------------
Jag Baddukonda
CSG


Original Message:
Sent: Oct 18, 2021 04:08
From: Filippo Roberto Valeriani
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Jonathan,
first of all thanks for your reply. In accordance with your reply, this mean that I should consider the resource"productRelationship "?
Thanks in advance for the reply,
Filippo


------------------------------
Filippo Roberto Valeriani
NTT DATA CORPORATION


Original Message:
Sent: Oct 17, 2021 05:14
From: Jonathan Goldberg
Subject: TMF622 Product Ordering API REST Specification - Blended order management

Hi Filippo
Typically a Product Order for new products is instantiated from one (or perhaps more than one) Product Offering. So if you had an offering that bundled device with accessories, your order would contain products derived from the bundling offering, the device and the accessories. But you can also create an order based on multiple offerings. It's entirely up to the way you want to manage your business.
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.