Open APIs

I see the following diagram in SID. Can I use this to group my product offerings, product offering prices, product specifications, discounts (POP alterations) etc. If so, how do I go about doing that? Also, I don't see TMF620 has anything representing these entities. Are these are internal use only and not exposed via standard APIs to the outside world?  

Hi Manu

There is already a Category pattern in the TMF620 Product Catalog API that may be used for grouping of product offerings within a catalog, but also for grouping of Product Specification as well (see below).  What kind of other grouping are you looking for?  There has been suggestions of adding tagging to the entities for management/maintenance purposes.

------------------------------
Dan d'Albuquerque
Entronica Company Limited

Original Message:
Sent: Feb 24, 2025 12:25
From: MMH HH
Subject: Support for RootEntityGroup

I see the following diagram in SID. Can I use this to group my product offerings, product offering prices, product specifications, discounts (POP alterations) etc. If so, how do I go about doing that? Also, I don't see TMF620 has anything representing these entities. Are these are internal use only and not exposed via standard APIs to the outside world?  

------------------------------
Manu
------------------------------

Thanks for the response, Dan!

I could use categories to group product offerings. Similarly I could use categories to group product specifications. However, once I group, I want to establish certain relationships between them. You can see below.

Basically, I want to model the following.

• A certain class/category of add-ons are only available for customers to buy if they have a certain class/category of plans. I don't want to do this at each add-on/plan PO level (which I could probably do with ProductOfferingRelationship).
  • e.g. unlimited roaming add-on on higher value mobile plans
•  A certain class/category of discounts are only available for customers with certain plans (POP with POs). I don't see any way to doing this currently.
  • e.g. 30% MRC discount is available only on staff-specific mobile plans
•  A certain class/category of discounts can't exist other class/category of discounts
  • e.g. some promo discounts with staff discount etc.

If I use category to model these "class" or groups, there is no way to establish relationship between (i.e. no CategoryRelationShip).

It would be great to understand from the community how they achieve these requirements.

------------------------------
Manu

Original Message:
Sent: Feb 25, 2025 01:38
From: Dan d'Albuquerque
Subject: Support for RootEntityGroup

Hi Manu

There is already a Category pattern in the TMF620 Product Catalog API that may be used for grouping of product offerings within a catalog, but also for grouping of Product Specification as well (see below).  What kind of other grouping are you looking for?  There has been suggestions of adding tagging to the entities for management/maintenance purposes.

------------------------------
Dan d'Albuquerque
Entronica Company Limited

Original Message:
Sent: Feb 24, 2025 12:25
From: MMH HH
Subject: Support for RootEntityGroup

I see the following diagram in SID. Can I use this to group my product offerings, product offering prices, product specifications, discounts (POP alterations) etc. If so, how do I go about doing that? Also, I don't see TMF620 has anything representing these entities. Are these are internal use only and not exposed via standard APIs to the outside world?  

------------------------------
Manu
------------------------------

Hi Manu

Is there any reason why you have ruled out the TMF679 Product Offering Qualification API (mechanism) and/or the TMF760 Product Configurator API (mechanism)?

Thanks for the response, Dan!

I could use categories to group product offerings. Similarly I could use categories to group product specifications. However, once I group, I want to establish certain relationships between them. You can see below.

Basically, I want to model the following.

• A certain class/category of add-ons are only available for customers to buy if they have a certain class/category of plans. I don't want to do this at each add-on/plan PO level (which I could probably do with ProductOfferingRelationship).
  • e.g. unlimited roaming add-on on higher value mobile plans
•  A certain class/category of discounts are only available for customers with certain plans (POP with POs). I don't see any way to doing this currently.
  • e.g. 30% MRC discount is available only on staff-specific mobile plans
•  A certain class/category of discounts can't exist other class/category of discounts
  • e.g. some promo discounts with staff discount etc.

If I use category to model these "class" or groups, there is no way to establish relationship between (i.e. no CategoryRelationShip).

It would be great to understand from the community how they achieve these requirements.

------------------------------
Manu

Original Message:
Sent: Feb 25, 2025 01:38
From: Dan d'Albuquerque
Subject: Support for RootEntityGroup

Hi Manu

There is already a Category pattern in the TMF620 Product Catalog API that may be used for grouping of product offerings within a catalog, but also for grouping of Product Specification as well (see below).  What kind of other grouping are you looking for?  There has been suggestions of adding tagging to the entities for management/maintenance purposes.

------------------------------
Dan d'Albuquerque
Entronica Company Limited

Original Message:
Sent: Feb 24, 2025 12:25
From: MMH HH
Subject: Support for RootEntityGroup

I see the following diagram in SID. Can I use this to group my product offerings, product offering prices, product specifications, discounts (POP alterations) etc. If so, how do I go about doing that? Also, I don't see TMF620 has anything representing these entities. Are these are internal use only and not exposed via standard APIs to the outside world?  

------------------------------
Manu
------------------------------

Thanks for the response, Dan. 

My understanding is that both these APIs need data to make use of and that data comes from product catalog configuration. Am I wrong?

Also, we're incrementally migrating from non-TMF to TMF. The first being product catalog (TMF620). We are not migrating all at once.

Hi Manu

Is there any reason why you have ruled out the TMF679 Product Offering Qualification API (mechanism) and/or the TMF760 Product Configurator API (mechanism)?

Thanks for the response, Dan!

I could use categories to group product offerings. Similarly I could use categories to group product specifications. However, once I group, I want to establish certain relationships between them. You can see below.

Basically, I want to model the following.

• A certain class/category of add-ons are only available for customers to buy if they have a certain class/category of plans. I don't want to do this at each add-on/plan PO level (which I could probably do with ProductOfferingRelationship).
  • e.g. unlimited roaming add-on on higher value mobile plans
•  A certain class/category of discounts are only available for customers with certain plans (POP with POs). I don't see any way to doing this currently.
  • e.g. 30% MRC discount is available only on staff-specific mobile plans
•  A certain class/category of discounts can't exist other class/category of discounts
  • e.g. some promo discounts with staff discount etc.

If I use category to model these "class" or groups, there is no way to establish relationship between (i.e. no CategoryRelationShip).

It would be great to understand from the community how they achieve these requirements.

------------------------------
Manu

Original Message:
Sent: Feb 25, 2025 01:38
From: Dan d'Albuquerque
Subject: Support for RootEntityGroup

Hi Manu

There is already a Category pattern in the TMF620 Product Catalog API that may be used for grouping of product offerings within a catalog, but also for grouping of Product Specification as well (see below).  What kind of other grouping are you looking for?  There has been suggestions of adding tagging to the entities for management/maintenance purposes.

------------------------------
Dan d'Albuquerque
Entronica Company Limited

Original Message:
Sent: Feb 24, 2025 12:25
From: MMH HH
Subject: Support for RootEntityGroup

I see the following diagram in SID. Can I use this to group my product offerings, product offering prices, product specifications, discounts (POP alterations) etc. If so, how do I go about doing that? Also, I don't see TMF620 has anything representing these entities. Are these are internal use only and not exposed via standard APIs to the outside world?  

------------------------------
Manu
------------------------------

Yes, both the TMF679 Product Offering Qualification and TMF760 Product Configurator requires information from TMF620 Product Catalog and TMF723 Policy Management.

Typically the offer qualification would check various parts of the Product catalog resources, including the relationship pattern (as you already mentioned) and the Policy (which handles most of your use cases above).  I appreciate though that you may not plan to implement TMF723 at this stage, but the information  model behind it could be used.

Thanks for the response, Dan. 

My understanding is that both these APIs need data to make use of and that data comes from product catalog configuration. Am I wrong?

Also, we're incrementally migrating from non-TMF to TMF. The first being product catalog (TMF620). We are not migrating all at once.

Hi Manu

Is there any reason why you have ruled out the TMF679 Product Offering Qualification API (mechanism) and/or the TMF760 Product Configurator API (mechanism)?

Thanks for the response, Dan!

I could use categories to group product offerings. Similarly I could use categories to group product specifications. However, once I group, I want to establish certain relationships between them. You can see below.

Basically, I want to model the following.

• A certain class/category of add-ons are only available for customers to buy if they have a certain class/category of plans. I don't want to do this at each add-on/plan PO level (which I could probably do with ProductOfferingRelationship).
  • e.g. unlimited roaming add-on on higher value mobile plans
•  A certain class/category of discounts are only available for customers with certain plans (POP with POs). I don't see any way to doing this currently.
  • e.g. 30% MRC discount is available only on staff-specific mobile plans
•  A certain class/category of discounts can't exist other class/category of discounts
  • e.g. some promo discounts with staff discount etc.

If I use category to model these "class" or groups, there is no way to establish relationship between (i.e. no CategoryRelationShip).

It would be great to understand from the community how they achieve these requirements.

------------------------------
Manu

Original Message:
Sent: Feb 25, 2025 01:38
From: Dan d'Albuquerque
Subject: Support for RootEntityGroup

Hi Manu

There is already a Category pattern in the TMF620 Product Catalog API that may be used for grouping of product offerings within a catalog, but also for grouping of Product Specification as well (see below).  What kind of other grouping are you looking for?  There has been suggestions of adding tagging to the entities for management/maintenance purposes.

------------------------------
Dan d'Albuquerque
Entronica Company Limited

Original Message:
Sent: Feb 24, 2025 12:25
From: MMH HH
Subject: Support for RootEntityGroup

I see the following diagram in SID. Can I use this to group my product offerings, product offering prices, product specifications, discounts (POP alterations) etc. If so, how do I go about doing that? Also, I don't see TMF620 has anything representing these entities. Are these are internal use only and not exposed via standard APIs to the outside world?  

------------------------------
Manu
------------------------------

Thanks for the response, Dan!

I could use categories to group product offerings. Similarly I could use categories to group product specifications. However, once I group, I want to establish certain relationships between them. You can see below.

Basically, I want to model the following.

• A certain class/category of add-ons are only available for customers to buy if they have a certain class/category of plans. I don't want to do this at each add-on/plan PO level (which I could probably do with ProductOfferingRelationship).
  • e.g. unlimited roaming add-on on higher value mobile plans
•  A certain class/category of discounts are only available for customers with certain plans (POP with POs). I don't see any way to doing this currently.
  • e.g. 30% MRC discount is available only on staff-specific mobile plans
•  A certain class/category of discounts can't exist other class/category of discounts
  • e.g. some promo discounts with staff discount etc.

If I use category to model these "class" or groups, there is no way to establish relationship between (i.e. no CategoryRelationShip).

It would be great to understand from the community how they achieve these requirements.

------------------------------
Manu

Original Message:
Sent: Feb 25, 2025 01:38
From: Dan d'Albuquerque
Subject: Support for RootEntityGroup

Hi Manu

There is already a Category pattern in the TMF620 Product Catalog API that may be used for grouping of product offerings within a catalog, but also for grouping of Product Specification as well (see below).  What kind of other grouping are you looking for?  There has been suggestions of adding tagging to the entities for management/maintenance purposes.

------------------------------
Dan d'Albuquerque
Entronica Company Limited

Original Message:
Sent: Feb 24, 2025 12:25
From: MMH HH
Subject: Support for RootEntityGroup

I see the following diagram in SID. Can I use this to group my product offerings, product offering prices, product specifications, discounts (POP alterations) etc. If so, how do I go about doing that? Also, I don't see TMF620 has anything representing these entities. Are these are internal use only and not exposed via standard APIs to the outside world?  

------------------------------
Manu
------------------------------

I see the following diagram in SID. Can I use this to group my product offerings, product offering prices, product specifications, discounts (POP alterations) etc. If so, how do I go about doing that? Also, I don't see TMF620 has anything representing these entities. Are these are internal use only and not exposed via standard APIs to the outside world?  

Hi Manu,

In SID, RootEntityGroup is the good concept to use for grouping  any Business Entity inhering from RootEntity such as product offerings, product offering prices, product specifications.

In addition, RootEntityGroup enables describing contraints between RootEntityGroups such as incompatible, requires... You may find illustrations of examples of contraints in the Pattern Domain guidebook.

You refer to the API, I'm not an API specialist at all but as far as I know they didn't introduce the concept of RootEntityGroup and use a Category that isn't a SID concept and is much less powerful.

So maybe you could ask if it could be added.

See you,

Cécile Gérardin (SID Leader)

I see the following diagram in SID. Can I use this to group my product offerings, product offering prices, product specifications, discounts (POP alterations) etc. If so, how do I go about doing that? Also, I don't see TMF620 has anything representing these entities. Are these are internal use only and not exposed via standard APIs to the outside world?