Hi Melissa
When an event is raised, there is generally no limitation on which software components can register as listeners to the event. So it's completely up to you.
The API profile document gives useful information on why the API was designed and some sample use cases. But the scenarios are Informative rather than Normative.
Just bear in mind that there will presumably need to be translation and mapping from an event that comes from the OSS domain to the corresponding BSS concepts, and you should consider carefully how to avoid data dependencies between domains.
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: Oct 31, 2023 12:48
From: Melissa Wu
Subject: Using TMF724 to communicate an incident to the BSS
Hi,
We have a requirement in which a major incident would be registered in the service management system, and a list of affected services would have to be sent to the BSS system, so that the affected end customers could be informed of the service disruption by the BSS.
We are considering using TMF724 (Incident Management) for this - notifications such as IncidentCreateEvent would be sent to the BSS.
However, looking at the example in "TMF724A_Incident_Management_API_Profile_v1.0.0" it seems that the API is being used only within the OSS space - a Network Domain Manager notifies an incident management system, which triggers a Trouble Ticket creation in the service management system.
Is there any guidance available on how to use this API, or how to handle the requirement I just described?
Are there reasons why we would not use this in communication with the BSS?
Thanks in advance.
------------------------------
Melissa Wu
Deutsche Glasfaser Management GmbH
------------------------------