We are looking for some guidance with the concept of 'Service Address' (Place) in the Open APIs for stationary services (non-mobile) and the relationship to customer.
We have a customer/enterprise with multiple service locations, GeographicPlace, where CE equipment/resources will reside.
When a Product is sold (TMF622-Product Order/TMF637-ProductMgt) there is a relationship between the Product and the 'Place' and the RelatedParty.
In TMF674-GeographicSite /673-Geogrpahic Address - there is a mapping from the site/place to the Related Party
Is this interetation the correct path to solve this:
We would like confirmation if this is the best approach or an alternative would be recommended
1. Define service addresses which are served by the CSP - (define Geographic Address using TMF673 - Geographic Address (which is a type of Place)
2. Define Prospect/Customer during the selling or early order process - (TMF629 - Customer Management)
3. Map the customer/partner to the available addresses - I can see using (TMF674 - Geographic Location to related party - as a type of place)
4. Then sell products to the available locations
alternatively addresses may be defined after the customer is onboarded. Both use cases are required.
We appreciate any guidance.
------------------------------
Tom Schnarr
ServiceNow, Inc.
------------------------------