Hi Ryan
I'm afraid that TMF ideology is that we associate prices
only with product offerings. Product offerings are what are sold.
And we must be very careful to use the word
service accurately. In your example, there is a
product (WAN), which has many
products (the access points at the sites). So when a customer wants to modify something at a site (e.g. to increase the bandwidth, or to substitute a more capable switch/router), she is modifying a
product.
The
service represents the underlying implementation of the product in the network. And the service might well be changed due to the modification of the pro
Hope this clarifies things.
------------------------------
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 18, 2022 02:47
From: Ryan Ruckley
Subject: Pricing for TMF633
Greetings,
We have a requirement to associate pricing with service catalogue items but I've noticed that pricing is only catered for within the product catalogue.
So either:
- I point my service catalogue specifications to a productOfferingPricing out of the productCatalogue or
- I find some other way to associate a price with a service catalogue entry.
In this model, a customer has bought a product (e.g. MPLS WAN) which has many services (individual sites) and they wish to modify a single service.
Am I correct in thinking that changes against an individual service should be listed in the service catalogue? Our business model currently has that some of these services are chargable but I can't see an obvious way to link a service catalogue item to a pricing record?
------------------------------
Ryan Ruckley
Principal Architect - Digital Transformation
Optus Enterprise & Business
------------------------------