I'm in a previous step: What are the possible values for relationshipType?
Examples in TMF620: reliesOn, discountedBy, OptionalFor, Dependency, DependsOn, relyOn
Examples by experience: changeableTo, contains, isChild, isParent, requires, exchangableTo
Although this can be customizable it whould be great if TMF defines a base standard.
Either we have a base definition and other needs improve the list of values or all the options are disputable :(
------------------------------
Gonçalo Furtado
Celfocus
------------------------------
Original Message:
Sent: Feb 24, 2022 09:39
From: David Whitfield
Subject: Understanding RelationShipType in Product Ordering TMF622 Release 17.5
Hi @Ludovic Robert,
in terms of the relationship scenario below we have a similar question.
,
Assuming that a set of of services are ordered and then committed to inventory (638) in the following example: -
Service 1 (Voice Service) --reliesOn---> Service 2 (Broardband) ---reliesOn----> Service 3 (fibreAccess)
How would the relationsips be modeled on Service 2 when requested via GET on service inventory (638). Clearly the relationship with Service 3 is reliesOn. But what about the relationship with Service 1.
cheers
Dave
------------------------------
David Whitfield
TalkTalk Group
Original Message:
Sent: Aug 21, 2019 11:19
From: Ludovic Robert
Subject: Understanding RelationShipType in Product Ordering TMF622 Release 17.5
Hello Rabinder
The relationship type is useful to qualify relation between 2 ordered product. We provided some examples in the API but implementation could define other.
If I provide examples from implementation experience:
- reliesOn is used when a technical prerequisite enforce to have a relationship between the product (and will be useful in service delivering). A mobile access must have a relies on on a sim card, a TV access must have a relies on on internet access for example. This relationship will be in the inventory and used in delivering. That's just examples and they could be described in other way - this is is not product modeling recommendation ;)
- brings is useful when 2 product are not tied technically but commercially. You want to keep thack in your inventory that this product A for example triggered this other product B selection. In future when customer will terminate A, it will allow you to automatically terminate B.
- hasParent/hasChild could be used to describe the commercial hierarchy. Suppose you order a Bundle A with product B and C. You can have 3 orderItems - the one for A will have hasChild relationship to orderItems describing ordering of B & C. OrderItem for B & C can have hasParent relationship to orderItem for A.
These are examples of implem but other relationship type could be added with defined semantic.
Hope it helps
Ludovic
------------------------------
Ludovic Robert
Orange
Original Message:
Sent: Aug 21, 2019 08:40
From: Rabinder Devnani
Subject: Understanding RelationShipType in Product Ordering TMF622 Release 17.5
Hi,
Need to understand what is the meaning of below values of RelationShipType used in orderItemRelationship between two orderItems
Values: reliesOn, brings, hasParent, hasChild
"orderItemRelationship":[
{
"id":"110",
"type":"reliesOn"
}
]
------------------------------
Rabinder Devnani
Sterlite Technologies Limited
------------------------------