Original Message:
Sent: Aug 01, 2024 05:41
From: Becca Reeves
Subject: TM Open APIs set by system
Hi Santiago,
As part of the ongoing work within the ODA Component Directory, we will be adding in more details such as the dependent APIs and also the eTOM (BPF) and SID relationships to the component pages. This work is ongoing and we are working towards providing greater visibility for relationships between assets. While we don't have a specific timeline on this yet, it is something we are aware of and your feedback is very valuable in helping us understand the requirements.
------------------------------
Becca Reeves
TM Forum
Original Message:
Sent: Jul 31, 2024 08:00
From: Santiago Lorente
Subject: TM Open APIs set by system
Thanks Jonathan for your reply,
before my post, I reviewed the ODA component map. A bit confusing the front page for a specific component, let's say "Service Order Management" (regarding the information about Open Apis). See below:
versus the one included in the specification document for that service order management ODA component (where the open api list is more exahustive)
So to avoid opening all the specificacion document, I miss a document with a high level view on the component interactions (with tmf open apis in).
Have a nice day!
------------------------------
Santiago Lorente
Salesforce
Original Message:
Sent: Jul 31, 2024 06:00
From: Jonathan Goldberg
Subject: TM Open APIs set by system
Hi Santiago
The concept of Application (as in TAM) is being quietly replaced by ODA components. The specification document for an ODA component includes lists of API operations that are consumed or provided by the component.
Bear in mind that the coverage by Open APIs of the entire telco space is incomplete, so it can be expected that there are new APIs to discover and specify.
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: Jul 31, 2024 04:12
From: Santiago Lorente
Subject: TM Open APIs set by system
Hi,
is there a document that list the set of TM Open APIs by application? For example for workforce management (Field Force Management), which are the inbound/outbound Open Apis required to covers all its interactions?
I want to know the whole set of Open Apis that the workforce management application requires to cover the whole set of interactions required by the different eTom processes in this area.
Resource | | | | |
| Resource Support Readiness | | |
| | Manage Field Workforce | |
| | | Manage Field Workforce Catalogs |
| | | | Administer Field Workforce Catalog |
| | | | Administer Organizations Catalog |
| | | | Administer Tools and Materials Catalog |
| | | | Configure Skill Catalog |
| | | | Administer Registration and Access |
| | | | Configure Logging and Audit |
| | | Manage Schedule & Appointments |
| | | | Configure Schedules |
| | | | Manage Schedule |
| | | | Determine Work Schedule |
| | | | Manage Reservations |
| | | | Manage Appointments |
| | | Plan & Forecast Field Workforce |
| | | | Forecast Demand |
| | | | Forecast Workforce Availability |
| | | | Adjust Durations |
Thanks
------------------------------
Santiago Lorente
Salesforce
------------------------------