Open APIs

Hello,

Currently we are implementing TMF compliant API to expose our CRM DataModel to external system. We were trying to understand few elements from TMF666 and we have different understanding or doubts such things. If somebody could give us hints how to approach following issues: 

1. if there is a place in TMF666 to reflect a BillingAccount to a Customer relationship, we considered a relatedParty but we are not sure if it could be used as we noticed that relatedParty should reference a party not a partyRole which is Customer. Additionally relatedParty is in relation with a contact, it is an aggregation relationship (related party requires contact), and what this contact could represent then ?

2. what is the meaning of a contact with regard to ContactMedium if we want to represent billing address which can be email or postalAddress. Our design is to have an email address, postal address on a billingAccount itself and we don't see any contact related data to map info tmf contact structure. Does the tmf structure suggests that rather than having an email and a postal address associated with a billing account, we should have it associated with a party and create o role like "bill receiver" and based on such structure generate tmf structure ?


version 4.0.1




I would appreciate any hints and discussion on this topic ? 

Best Regards,
Marcin

------------------------------
Marcin Gizka
TO BE VERIFIED
------------------------------

Hi Marcin
For your point 1.: the RelatedParty structure is a dual-purpose reference that allows you to point directly to a Party (organization or individual) or to a PartyRole (e.g. Customer). 
For your point 2.: I believe that the purpose of the Contact sub-entity is to define people who are related to the bill; contact includes a contact medium that has an email address

Hope it helps

------------------------------
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: Mar 16, 2022 03:59
From: Marcin Gizka
Subject: TMF666, Customer reference from BillingAccount and BillingAccountAddress representation questions

Hello,

Currently we are implementing TMF compliant API to expose our CRM DataModel to external system. We were trying to understand few elements from TMF666 and we have different understanding or doubts such things. If somebody could give us hints how to approach following issues:

1. if there is a place in TMF666 to reflect a BillingAccount to a Customer relationship, we considered a relatedParty but we are not sure if it could be used as we noticed that relatedParty should reference a party not a partyRole which is Customer. Additionally relatedParty is in relation with a contact, it is an aggregation relationship (related party requires contact), and what this contact could represent then ?

2. what is the meaning of a contact with regard to ContactMedium if we want to represent billing address which can be email or postalAddress. Our design is to have an email address, postal address on a billingAccount itself and we don't see any contact related data to map info tmf contact structure. Does the tmf structure suggests that rather than having an email and a postal address associated with a billing account, we should have it associated with a party and create o role like "bill receiver" and based on such structure generate tmf structure ?


version 4.0.1

I would appreciate any hints and discussion on this topic ?

Best Regards,
Marcin

------------------------------
Marcin Gizka
TO BE VERIFIED
------------------------------

Hello Jonathan,

Thank you for your reply. 

Ad1.  Yes, that is true. I was wondering what contact entity would mean in such structure which I think is mandatory in the model ?
Ad2. OK, do you maybe know why this model is different than in the Customer Management, where we have a Customer entity associated directly to a ContactMedium structure ?

Best Regards, 
Marcin

------------------------------
Marcin Gizka
TO BE VERIFIED
------------------------------

Original Message:
Sent: Mar 18, 2022 09:50
From: Jonathan Goldberg
Subject: TMF666, Customer reference from BillingAccount and BillingAccountAddress representation questions

Hi Marcin
For your point 1.: the RelatedParty structure is a dual-purpose reference that allows you to point directly to a Party (organization or individual) or to a PartyRole (e.g. Customer).
For your point 2.: I believe that the purpose of the Contact sub-entity is to define people who are related to the bill; contact includes a contact medium that has an email address

Hope it helps

------------------------------
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: Mar 16, 2022 03:59
From: Marcin Gizka
Subject: TMF666, Customer reference from BillingAccount and BillingAccountAddress representation questions

Hello,

Currently we are implementing TMF compliant API to expose our CRM DataModel to external system. We were trying to understand few elements from TMF666 and we have different understanding or doubts such things. If somebody could give us hints how to approach following issues:

1. if there is a place in TMF666 to reflect a BillingAccount to a Customer relationship, we considered a relatedParty but we are not sure if it could be used as we noticed that relatedParty should reference a party not a partyRole which is Customer. Additionally relatedParty is in relation with a contact, it is an aggregation relationship (related party requires contact), and what this contact could represent then ?

2. what is the meaning of a contact with regard to ContactMedium if we want to represent billing address which can be email or postalAddress. Our design is to have an email address, postal address on a billingAccount itself and we don't see any contact related data to map info tmf contact structure. Does the tmf structure suggests that rather than having an email and a postal address associated with a billing account, we should have it associated with a party and create o role like "bill receiver" and based on such structure generate tmf structure ?


version 4.0.1

I would appreciate any hints and discussion on this topic ?

Best Regards,
Marcin

------------------------------
Marcin Gizka
TO BE VERIFIED
------------------------------

Hi Marcin
Glad I was able to help a bit.
To be honest, I have no idea why Contact exists only in the context of the Account entity (and its subclasses). In my book, a Contact is a first-class PartyRole (but played only by an individual - doesn't make sense for an Organization to play role of Contact), but I can't see that the Open API model will change in the near future.

------------------------------
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: Mar 21, 2022 11:17
From: Marcin Gizka
Subject: TMF666, Customer reference from BillingAccount and BillingAccountAddress representation questions

Hello Jonathan,

Thank you for your reply.

Ad1.  Yes, that is true. I was wondering what contact entity would mean in such structure which I think is mandatory in the model ?
Ad2. OK, do you maybe know why this model is different than in the Customer Management, where we have a Customer entity associated directly to a ContactMedium structure ?

Best Regards,
Marcin

------------------------------
Marcin Gizka
TO BE VERIFIED

Original Message:
Sent: Mar 18, 2022 09:50
From: Jonathan Goldberg
Subject: TMF666, Customer reference from BillingAccount and BillingAccountAddress representation questions

Hi Marcin
For your point 1.: the RelatedParty structure is a dual-purpose reference that allows you to point directly to a Party (organization or individual) or to a PartyRole (e.g. Customer).
For your point 2.: I believe that the purpose of the Contact sub-entity is to define people who are related to the bill; contact includes a contact medium that has an email address

Hope it helps

------------------------------
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: Mar 16, 2022 03:59
From: Marcin Gizka
Subject: TMF666, Customer reference from BillingAccount and BillingAccountAddress representation questions

Hello,

Currently we are implementing TMF compliant API to expose our CRM DataModel to external system. We were trying to understand few elements from TMF666 and we have different understanding or doubts such things. If somebody could give us hints how to approach following issues:

1. if there is a place in TMF666 to reflect a BillingAccount to a Customer relationship, we considered a relatedParty but we are not sure if it could be used as we noticed that relatedParty should reference a party not a partyRole which is Customer. Additionally relatedParty is in relation with a contact, it is an aggregation relationship (related party requires contact), and what this contact could represent then ?

2. what is the meaning of a contact with regard to ContactMedium if we want to represent billing address which can be email or postalAddress. Our design is to have an email address, postal address on a billingAccount itself and we don't see any contact related data to map info tmf contact structure. Does the tmf structure suggests that rather than having an email and a postal address associated with a billing account, we should have it associated with a party and create o role like "bill receiver" and based on such structure generate tmf structure ?


version 4.0.1

I would appreciate any hints and discussion on this topic ?

Best Regards,
Marcin

------------------------------
Marcin Gizka
TO BE VERIFIED
------------------------------

Thank you Jonathan for sharing this.

Indeed you helped.

------------------------------
Marcin Gizka
TO BE VERIFIED
------------------------------

Original Message:
Sent: Mar 21, 2022 15:07
From: Jonathan Goldberg
Subject: TMF666, Customer reference from BillingAccount and BillingAccountAddress representation questions

Hi Marcin
Glad I was able to help a bit.
To be honest, I have no idea why Contact exists only in the context of the Account entity (and its subclasses). In my book, a Contact is a first-class PartyRole (but played only by an individual - doesn't make sense for an Organization to play role of Contact), but I can't see that the Open API model will change in the near future.

------------------------------
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: Mar 21, 2022 11:17
From: Marcin Gizka
Subject: TMF666, Customer reference from BillingAccount and BillingAccountAddress representation questions

Hello Jonathan,

Thank you for your reply.

Ad1.  Yes, that is true. I was wondering what contact entity would mean in such structure which I think is mandatory in the model ?
Ad2. OK, do you maybe know why this model is different than in the Customer Management, where we have a Customer entity associated directly to a ContactMedium structure ?

Best Regards,
Marcin

------------------------------
Marcin Gizka
TO BE VERIFIED

Original Message:
Sent: Mar 18, 2022 09:50
From: Jonathan Goldberg
Subject: TMF666, Customer reference from BillingAccount and BillingAccountAddress representation questions

Hi Marcin
For your point 1.: the RelatedParty structure is a dual-purpose reference that allows you to point directly to a Party (organization or individual) or to a PartyRole (e.g. Customer).
For your point 2.: I believe that the purpose of the Contact sub-entity is to define people who are related to the bill; contact includes a contact medium that has an email address

Hope it helps

------------------------------
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: Mar 16, 2022 03:59
From: Marcin Gizka
Subject: TMF666, Customer reference from BillingAccount and BillingAccountAddress representation questions

Hello,

Currently we are implementing TMF compliant API to expose our CRM DataModel to external system. We were trying to understand few elements from TMF666 and we have different understanding or doubts such things. If somebody could give us hints how to approach following issues:

1. if there is a place in TMF666 to reflect a BillingAccount to a Customer relationship, we considered a relatedParty but we are not sure if it could be used as we noticed that relatedParty should reference a party not a partyRole which is Customer. Additionally relatedParty is in relation with a contact, it is an aggregation relationship (related party requires contact), and what this contact could represent then ?

2. what is the meaning of a contact with regard to ContactMedium if we want to represent billing address which can be email or postalAddress. Our design is to have an email address, postal address on a billingAccount itself and we don't see any contact related data to map info tmf contact structure. Does the tmf structure suggests that rather than having an email and a postal address associated with a billing account, we should have it associated with a party and create o role like "bill receiver" and based on such structure generate tmf structure ?


version 4.0.1

I would appreciate any hints and discussion on this topic ?

Best Regards,
Marcin

------------------------------
Marcin Gizka
TO BE VERIFIED
------------------------------