Looking through TMF625_API_Data_Model it is apparent that there has been a heavy focus on exploring Product, Billing and Customer at the expense of Service and Resource. It appears this is further reflected (although to a lesser extent) in the Open API's. Such things as the relationships between service specs and usage specs, service and usage, service and alarms/faults and services and listeners.
The latest versions of the document appear to be 2016 releases. Are there any working documents that show the foundation data structure upon which the API specs are built? Whilst I can see each spec has UML models, these models do not present a connected view that addresses full service perspectives that we need.
------------------------------
Stuart Batten
Telstra Corporation
------------------------------