We're currently in process of moving from a custom product catalog solution to one using TMForum as a standard. I'm trying to decide if I'm thinking too much what we've done in the past vs. what TMF standards are designed for. Right now, I feel like I'm 'guessing' too much.
Product offering prices feel too simplified. It's easy enough to determine the main price and the associated taxes. HOWEVER, what if a product as an MRC AND an NRC? What if there are fees associated to the product? What if there's compound pricing that needs to be shown to the user?
This is particularly applicable to phone where we have multiple regulatory fees that are required on top of our charges for the service. Placing the fees in the 'taxItem' values seems like an abuse of the spec.
Would it be appropriate to use the popRelationship to define a fee as 'requiredBy' another POP? Is there a valid list of relationship types that we should be looking at?
Maybe this is a fundamental misunderstanding I have about providing an offering vs. providing details during the buy-flow, but it feels like this information would be required up front for the end user.
I've found a lot of great information and resources in this forum, so thank you in advance!
------------------------------
Jason Funk
MetroNet
------------------------------