Thank you all for your insights into this subject.
After reading the feed and the documentation again, these are my observations.
In reference to the API documentation examples, what constitutes an underlying problem seems to be a judgement call from the SPM Administrator. In the example, it's the fact that the Administrator considers that two declared problems affecting the same location results in a Problem, Underlying Problem relationship. It would be nice if the rules governing when a problem becomes an underlying problem were more explicit. For example, an underlying relationship is established when:
- They have the same underlying cause.
- They affect the same location.
- An affected service in one problem is dependent on an affected service in another problem.
I am assuming as well that in a Problem-Underlying-Problem that both problems are handled individually whereas in a Parent-Child association, only the Parent problem is handled and when closed, closes all children as well. Is this a correct assumption?
From what I understand from the Parent-Child(ren) example, The Parent relationship is simply a way of grouping Service Problems based on some criteria. In the example, the criteria is that Problem 1 and 2 are deemed to be the same problem. Again, it would be nice if the rules for grouping were more explicit, or maybe they are too CSP/telco. specific.
Thanks again
------------------------------
Wayne Sampson
CGI Info Systems Management Consulting Inc.
------------------------------
Original Message:
Sent: Apr 13, 2021 02:08
From: Jonathan Goldberg
Subject: TMF656 Parent/Underlying Problem explanation
Hi Wayne
I hope this example is accurate, but I am not an OSS expert.
Let's suppose that telco partners start experiencing connectivity issues with (say) a 1GB fiber connection. They'll each open a service problem. But the root of the problems is the same for all, the equipment in the telco's exchange that handles all the fiber connections. So the telco could open a problem to get that equipment fixed, and make the problem a parent problem for all the partners' problems.
Similar concept to customer trouble ticket, there could be 1000s of retail trouble tickets opened all due to the same underlying problem.
Happy for OSS ops experts to weigh in with more (better?) examples.
Anyway 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: Apr 12, 2021 15:33
From: Wayne Sampson
Subject: TMF656 Parent/Underlying Problem explanation
Hi, can someone explain what constitutes a Parent or Underlying Service problem, preferably with an example.
Thanks
------------------------------
Wayne Sampson
CGI Info Systems Management Consulting Inc.
------------------------------