TM Forum Community

Hi!

I'm pretty new with TM Forum and SID, currently analyzing how to structure our data to conform to SID as much as possible. We have in our legacy systems data about customer representative, how this should be reflected with SID, is it a PartyRole to be defined in our architecture? Any of you have already performed that, how did you make it?

Any example or suggestion are welcome!

Thanks

Hi Francois,

Welcome to the TM Forum!

A Customer Representative is a PartyRole.   Taking it a step further, a Customer Representative is a PartyRole in the Customer domain.   In the Customer Domain, there is an ABE called Customer Party Roles ABE.  The definition of that ABE is as follows:

The Customer Party Roles ABE is the focus on all the PartyRoles related to Customer.  

Figure C.00 specifies some PartyRoles in the customer domain as follows:

One could consider if Customer Representative is the same as a CustomerServiceRepresentative.   

One can add additional PartyRoles explicitly by sub-classing PartyRole.   Alternatively, one could use the Specification Entity / Entity pattern to add additional PartyRoles.

I hope this helps!

Hi!

I'm pretty new with TM Forum and SID, currently analyzing how to structure our data to conform to SID as much as possible. We have in our legacy systems data about customer representative, how this should be reflected with SID, is it a PartyRole to be defined in our architecture? Any of you have already performed that, how did you make it?

Any example or suggestion are welcome!

Thanks

Hi Kevin!

Thank you for your answer! You confirmed my thought that it could be performed by sub-classing the PartyRole or thru the addition of a PartyRole thru the EntityPattern. I would not go with considering CustomerServiceRepresentative because I feel like it will be used to represent our CSRs. Now I have to decide which path is best (sub-classing vs Entity patter), do you know if there is a best praticie about it?

Hi Francois,

Welcome to the TM Forum!

A Customer Representative is a PartyRole.   Taking it a step further, a Customer Representative is a PartyRole in the Customer domain.   In the Customer Domain, there is an ABE called Customer Party Roles ABE.  The definition of that ABE is as follows:

The Customer Party Roles ABE is the focus on all the PartyRoles related to Customer.  

Figure C.00 specifies some PartyRoles in the customer domain as follows:

One could consider if Customer Representative is the same as a CustomerServiceRepresentative.   

One can add additional PartyRoles explicitly by sub-classing PartyRole.   Alternatively, one could use the Specification Entity / Entity pattern to add additional PartyRoles.

I hope this helps!

Hi!

I'm pretty new with TM Forum and SID, currently analyzing how to structure our data to conform to SID as much as possible. We have in our legacy systems data about customer representative, how this should be reflected with SID, is it a PartyRole to be defined in our architecture? Any of you have already performed that, how did you make it?

Any example or suggestion are welcome!

Thanks

Hi François

The main reason to subclass is that it gives you a concrete and strongly-typed model for your data. This becomes important when you expose the data with APIs, such as TM Forum Open APIs. In the Open API program, we have a concrete subclass of PartyRole for Customer itself, but most other party roles are defined dynamically, using party role specification.

Hope it helps

Hi Kevin!

Thank you for your answer! You confirmed my thought that it could be performed by sub-classing the PartyRole or thru the addition of a PartyRole thru the EntityPattern. I would not go with considering CustomerServiceRepresentative because I feel like it will be used to represent our CSRs. Now I have to decide which path is best (sub-classing vs Entity patter), do you know if there is a best praticie about it?

Hi Francois,

Welcome to the TM Forum!

A Customer Representative is a PartyRole.   Taking it a step further, a Customer Representative is a PartyRole in the Customer domain.   In the Customer Domain, there is an ABE called Customer Party Roles ABE.  The definition of that ABE is as follows:

The Customer Party Roles ABE is the focus on all the PartyRoles related to Customer.  

Figure C.00 specifies some PartyRoles in the customer domain as follows:

One could consider if Customer Representative is the same as a CustomerServiceRepresentative.   

One can add additional PartyRoles explicitly by sub-classing PartyRole.   Alternatively, one could use the Specification Entity / Entity pattern to add additional PartyRoles.

I hope this helps!

Hi!

I'm pretty new with TM Forum and SID, currently analyzing how to structure our data to conform to SID as much as possible. We have in our legacy systems data about customer representative, how this should be reflected with SID, is it a PartyRole to be defined in our architecture? Any of you have already performed that, how did you make it?

Any example or suggestion are welcome!

Thanks