Open APIs

Hello community, 

I am looking for concrete examples on how TMF 723 is being used? What kind of policies and rules is it addressing?

Specially interested how product catalog offers/products related rules are being represented within TMF723.

Any guidance is appreciated.

Thanks!

------------------------------
Gladson Russo
Salesforce
------------------------------

hi,

typical examples of policies in product domain:

• Product eligibility: customer segment, credit score, B2B/B2C, address/coverage.
• Product Configuration: requires/excludes, min/max quantities, mutually exclusive choices.
• dynamic pricing and discounts
• product terms (notice period, binding, termination fees...)

but it works on other domains too:

• Compliance & security: KYC, GDPR consent, role-based actions.
• Network/service controls: throttle tiers, QoS profiles, fair-use triggers.

• Customer care exceptions: supervisor-only waivers, goodwill adjustments

I did some research on policy, I would recommend these 2 publications on TMF main website:

1. examples of policies using ECA business rule model: GB922 Product Guide (SID) and I think there is some information in the common guide.
2. IG1220B Business Rule - Conceptual Information & Data Model v2.0.0 (interesting but this duplicates a lot of work already done in GB922/SID)

TMF760 API user guide  has info on how to integrate Configurator with Policy.

Also, for clarification as people sometimes expect something different of policies:

1. TMF723 is the PAP interface to define, organize, and manage policies, conditions, actions, catalogs, and domains (using the ECA model). TMF723 API only defines endpoints for policy management resources.
2. TMF723 is not a runtime PDP (Policy Decision Point, but TMF calls it "Policy Application"): it cannot evaluate policies or return permit/deny decisions for enforcement. OCA-C TMF0027 Product Configurator is the PDP.

------------------------------
Kind regards,

Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS

Original Message:
Sent: Sep 20, 2025 09:04
From: Gladson Russo
Subject: TMF 723 - Concrete Cases Examples and Guidance

Hello community, 

I am looking for concrete examples on how TMF 723 is being used? What kind of policies and rules is it addressing?

Specially interested how product catalog offers/products related rules are being represented within TMF723.

Any guidance is appreciated.

Thanks!

------------------------------
Gladson Russo
Salesforce
------------------------------

Hi Matthieu,

Thanks for the great summary - especially the clarification around TMF723 as a PAP interface and not a runtime PDP.

I'd like to add that while TMF723 is essential for managing complex ECA-based policies, many foundational business rules can be modelled directly within the product catalog using TMF620. This includes:

• Eligibility and compatibility rules via productOfferingRelationship (e.g., requires, excludes, optionalFor)

• Bundling logic using isBundle and bundledFrom relationships

• Basic constraints like sellability, availability, and channel-specific visibility

These catalog-based relationships allow "some" expression of business logic - especially useful for guiding product configuration and order validation, even before invoking external policy engines.

In your experience, when does it make sense to use policies instead of relying on catalog-based rules?

hi,

typical examples of policies in product domain:

• Product eligibility: customer segment, credit score, B2B/B2C, address/coverage.
• Product Configuration: requires/excludes, min/max quantities, mutually exclusive choices.
• dynamic pricing and discounts
• product terms (notice period, binding, termination fees...)

but it works on other domains too:

• Compliance & security: KYC, GDPR consent, role-based actions.
• Network/service controls: throttle tiers, QoS profiles, fair-use triggers.

• Customer care exceptions: supervisor-only waivers, goodwill adjustments

I did some research on policy, I would recommend these 2 publications on TMF main website:

1. examples of policies using ECA business rule model: GB922 Product Guide (SID) and I think there is some information in the common guide.
2. IG1220B Business Rule - Conceptual Information & Data Model v2.0.0 (interesting but this duplicates a lot of work already done in GB922/SID)

TMF760 API user guide  has info on how to integrate Configurator with Policy.

Also, for clarification as people sometimes expect something different of policies:

1. TMF723 is the PAP interface to define, organize, and manage policies, conditions, actions, catalogs, and domains (using the ECA model). TMF723 API only defines endpoints for policy management resources.
2. TMF723 is not a runtime PDP (Policy Decision Point, but TMF calls it "Policy Application"): it cannot evaluate policies or return permit/deny decisions for enforcement. OCA-C TMF0027 Product Configurator is the PDP.

------------------------------
Kind regards,

Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS

Original Message:
Sent: Sep 20, 2025 09:04
From: Gladson Russo
Subject: TMF 723 - Concrete Cases Examples and Guidance

Hello community, 

I am looking for concrete examples on how TMF 723 is being used? What kind of policies and rules is it addressing?

Specially interested how product catalog offers/products related rules are being represented within TMF723.

Any guidance is appreciated.

Thanks!

------------------------------
Gladson Russo
Salesforce
------------------------------

Hi Matthieu,

Thanks for the great summary - especially the clarification around TMF723 as a PAP interface and not a runtime PDP.

I'd like to add that while TMF723 is essential for managing complex ECA-based policies, many foundational business rules can be modelled directly within the product catalog using TMF620. This includes:

• Eligibility and compatibility rules via productOfferingRelationship (e.g., requires, excludes, optionalFor)

• Bundling logic using isBundle and bundledFrom relationships

• Basic constraints like sellability, availability, and channel-specific visibility

These catalog-based relationships allow "some" expression of business logic - especially useful for guiding product configuration and order validation, even before invoking external policy engines.

In your experience, when does it make sense to use policies instead of relying on catalog-based rules?

------------------------------
Jan Brnka
T-Mobile Czech & Slovak Telekom, a.s.

Original Message:
Sent: Sep 23, 2025 07:22
From: Matthieu Hattab
Subject: TMF 723 - Concrete Cases Examples and Guidance

hi,

typical examples of policies in product domain:

• Product eligibility: customer segment, credit score, B2B/B2C, address/coverage.
• Product Configuration: requires/excludes, min/max quantities, mutually exclusive choices.
• dynamic pricing and discounts
• product terms (notice period, binding, termination fees...)

but it works on other domains too:

• Compliance & security: KYC, GDPR consent, role-based actions.
• Network/service controls: throttle tiers, QoS profiles, fair-use triggers.

• Customer care exceptions: supervisor-only waivers, goodwill adjustments

I did some research on policy, I would recommend these 2 publications on TMF main website:

1. examples of policies using ECA business rule model: GB922 Product Guide (SID) and I think there is some information in the common guide.
2. IG1220B Business Rule - Conceptual Information & Data Model v2.0.0 (interesting but this duplicates a lot of work already done in GB922/SID)

TMF760 API user guide  has info on how to integrate Configurator with Policy.

Also, for clarification as people sometimes expect something different of policies:

1. TMF723 is the PAP interface to define, organize, and manage policies, conditions, actions, catalogs, and domains (using the ECA model). TMF723 API only defines endpoints for policy management resources.
2. TMF723 is not a runtime PDP (Policy Decision Point, but TMF calls it "Policy Application"): it cannot evaluate policies or return permit/deny decisions for enforcement. OCA-C TMF0027 Product Configurator is the PDP.

------------------------------
Kind regards,

Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS

Original Message:
Sent: Sep 20, 2025 09:04
From: Gladson Russo
Subject: TMF 723 - Concrete Cases Examples and Guidance

Hello community, 

I am looking for concrete examples on how TMF 723 is being used? What kind of policies and rules is it addressing?

Specially interested how product catalog offers/products related rules are being represented within TMF723.

Any guidance is appreciated.

Thanks!

------------------------------
Gladson Russo
Salesforce
------------------------------

my personal choices:

Pricing:

• simple pricing-> product catalogue
  • (including term-specific and charValue-specific prices, simple discount, taxes)
• anything else -> external rule catalogue with a policyRef in the product catalogue
• there was an (aborted?) attempt about a year and half ago by Jonathan Goldberg to make a significant extension to the ProductOfferingPrice resource in 620 to support dynamic pricing. But since he left his job, nobody else picked up the role and it seems 620 is not seing any further development.

Anything bundle

• product catalogue

(commercial) eligibility

• external rule catalogue with a policyRef in the product catalogue
  • most eligibility rules have complexity that are better modelled with Policy model (ECA) or similar models (DMN, FEEL...) 

productofferingRelationships

• It's a very simple relationship between 2 offers. Only for simple rules

If you have a rule engine and rule management,  the product catalogue could just declare:

• PO: offer name,  lifecycle and catalogue categories...
• POP: offer price(s) (one-time, recurring, usage etc)
• PS: product specification
• BPO: bundled offers, cardinalities, product groups
• Product Actions
• PolicyRef: reference rule id managed and computed externally

My 2 cents

------------------------------
Kind regards,

Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS

Original Message:
Sent: Sep 25, 2025 05:22
From: Jan Brnka
Subject: TMF 723 - Concrete Cases Examples and Guidance

Hi Matthieu,

Thanks for the great summary - especially the clarification around TMF723 as a PAP interface and not a runtime PDP.

I'd like to add that while TMF723 is essential for managing complex ECA-based policies, many foundational business rules can be modelled directly within the product catalog using TMF620. This includes:

• Eligibility and compatibility rules via productOfferingRelationship (e.g., requires, excludes, optionalFor)

• Bundling logic using isBundle and bundledFrom relationships

• Basic constraints like sellability, availability, and channel-specific visibility

These catalog-based relationships allow "some" expression of business logic - especially useful for guiding product configuration and order validation, even before invoking external policy engines.

In your experience, when does it make sense to use policies instead of relying on catalog-based rules?

------------------------------
Jan Brnka
T-Mobile Czech & Slovak Telekom, a.s.

Original Message:
Sent: Sep 23, 2025 07:22
From: Matthieu Hattab
Subject: TMF 723 - Concrete Cases Examples and Guidance

hi,

typical examples of policies in product domain:

• Product eligibility: customer segment, credit score, B2B/B2C, address/coverage.
• Product Configuration: requires/excludes, min/max quantities, mutually exclusive choices.
• dynamic pricing and discounts
• product terms (notice period, binding, termination fees...)

but it works on other domains too:

• Compliance & security: KYC, GDPR consent, role-based actions.
• Network/service controls: throttle tiers, QoS profiles, fair-use triggers.

• Customer care exceptions: supervisor-only waivers, goodwill adjustments

I did some research on policy, I would recommend these 2 publications on TMF main website:

1. examples of policies using ECA business rule model: GB922 Product Guide (SID) and I think there is some information in the common guide.
2. IG1220B Business Rule - Conceptual Information & Data Model v2.0.0 (interesting but this duplicates a lot of work already done in GB922/SID)

TMF760 API user guide  has info on how to integrate Configurator with Policy.

Also, for clarification as people sometimes expect something different of policies:

1. TMF723 is the PAP interface to define, organize, and manage policies, conditions, actions, catalogs, and domains (using the ECA model). TMF723 API only defines endpoints for policy management resources.
2. TMF723 is not a runtime PDP (Policy Decision Point, but TMF calls it "Policy Application"): it cannot evaluate policies or return permit/deny decisions for enforcement. OCA-C TMF0027 Product Configurator is the PDP.

------------------------------
Kind regards,

Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS

Original Message:
Sent: Sep 20, 2025 09:04
From: Gladson Russo
Subject: TMF 723 - Concrete Cases Examples and Guidance

Hello community, 

I am looking for concrete examples on how TMF 723 is being used? What kind of policies and rules is it addressing?

Specially interested how product catalog offers/products related rules are being represented within TMF723.

Any guidance is appreciated.

Thanks!

------------------------------
Gladson Russo
Salesforce
------------------------------

I see only the API spec YAML for 723. I don't see user guide and other documents. Are they in the confluence?

my personal choices:

Pricing:

• simple pricing-> product catalogue
  • (including term-specific and charValue-specific prices, simple discount, taxes)
• anything else -> external rule catalogue with a policyRef in the product catalogue
• there was an (aborted?) attempt about a year and half ago by Jonathan Goldberg to make a significant extension to the ProductOfferingPrice resource in 620 to support dynamic pricing. But since he left his job, nobody else picked up the role and it seems 620 is not seing any further development.

Anything bundle

• product catalogue

(commercial) eligibility

• external rule catalogue with a policyRef in the product catalogue
  • most eligibility rules have complexity that are better modelled with Policy model (ECA) or similar models (DMN, FEEL...) 

productofferingRelationships

• It's a very simple relationship between 2 offers. Only for simple rules

If you have a rule engine and rule management,  the product catalogue could just declare:

• PO: offer name,  lifecycle and catalogue categories...
• POP: offer price(s) (one-time, recurring, usage etc)
• PS: product specification
• BPO: bundled offers, cardinalities, product groups
• Product Actions
• PolicyRef: reference rule id managed and computed externally

My 2 cents

------------------------------
Kind regards,

Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS

Original Message:
Sent: Sep 25, 2025 05:22
From: Jan Brnka
Subject: TMF 723 - Concrete Cases Examples and Guidance

Hi Matthieu,

Thanks for the great summary - especially the clarification around TMF723 as a PAP interface and not a runtime PDP.

I'd like to add that while TMF723 is essential for managing complex ECA-based policies, many foundational business rules can be modelled directly within the product catalog using TMF620. This includes:

• Eligibility and compatibility rules via productOfferingRelationship (e.g., requires, excludes, optionalFor)

• Bundling logic using isBundle and bundledFrom relationships

• Basic constraints like sellability, availability, and channel-specific visibility

These catalog-based relationships allow "some" expression of business logic - especially useful for guiding product configuration and order validation, even before invoking external policy engines.

In your experience, when does it make sense to use policies instead of relying on catalog-based rules?

------------------------------
Jan Brnka
T-Mobile Czech & Slovak Telekom, a.s.

Original Message:
Sent: Sep 23, 2025 07:22
From: Matthieu Hattab
Subject: TMF 723 - Concrete Cases Examples and Guidance

hi,

typical examples of policies in product domain:

• Product eligibility: customer segment, credit score, B2B/B2C, address/coverage.
• Product Configuration: requires/excludes, min/max quantities, mutually exclusive choices.
• dynamic pricing and discounts
• product terms (notice period, binding, termination fees...)

but it works on other domains too:

• Compliance & security: KYC, GDPR consent, role-based actions.
• Network/service controls: throttle tiers, QoS profiles, fair-use triggers.

• Customer care exceptions: supervisor-only waivers, goodwill adjustments

I did some research on policy, I would recommend these 2 publications on TMF main website:

1. examples of policies using ECA business rule model: GB922 Product Guide (SID) and I think there is some information in the common guide.
2. IG1220B Business Rule - Conceptual Information & Data Model v2.0.0 (interesting but this duplicates a lot of work already done in GB922/SID)

TMF760 API user guide  has info on how to integrate Configurator with Policy.

Also, for clarification as people sometimes expect something different of policies:

1. TMF723 is the PAP interface to define, organize, and manage policies, conditions, actions, catalogs, and domains (using the ECA model). TMF723 API only defines endpoints for policy management resources.
2. TMF723 is not a runtime PDP (Policy Decision Point, but TMF calls it "Policy Application"): it cannot evaluate policies or return permit/deny decisions for enforcement. OCA-C TMF0027 Product Configurator is the PDP.

------------------------------
Kind regards,

Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS

Original Message:
Sent: Sep 20, 2025 09:04
From: Gladson Russo
Subject: TMF 723 - Concrete Cases Examples and Guidance

Hello community, 

I am looking for concrete examples on how TMF 723 is being used? What kind of policies and rules is it addressing?

Specially interested how product catalog offers/products related rules are being represented within TMF723.

Any guidance is appreciated.

Thanks!

------------------------------
Gladson Russo
Salesforce
------------------------------