Hi,
I'm not sure it helps, but I can share our experience. At Marand, we developed a SID-based unified product catalog that drives most BSS components. To make a single internet product offering for all bandwidths possible, we extended our internal implementation of the SID with a concept called 'parametric price'.
We simply associated characteristic's domain elements with price amounts. The simplest version is a single-characteristic price (e.g. bandwidth drives the amount selection). The more complex version is when several characteristics drive the amount selection (e.g. L1 technology {fiber, copper, LTE,...}, L2 technology {ADSL, VDSL,....}, and bandwidth). The bandwidth characteristic is normally used for service provisioning, so the main benefit of characteristic-driven prices is to ensure OSS provisions the same characteristic value that BSS (billing) charges. This way, you prevent revenue leaks.
On the other hand, we approached the solution with several product offerings when there was a necessity to establish relationships between the internet offering and different parent offerings (e.g. bundles), different child offerings (e.g. add-ons) or in case of different accounting rules based on the offering.
Hope you'll find this useful.
Regards,
------------------------------
Bostjan Keber, Think!PLM product manager,
Marand d.o.o.
------------------------------