System and method for classifying and resolving software production incident
US-2018032330-A9 · Feb 1, 2018 · US
US10547507B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10547507-B2 |
| Application number | US-201815963458-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 26, 2018 |
| Priority date | Dec 22, 2015 |
| Publication date | Jan 28, 2020 |
| Grant date | Jan 28, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method includes obtaining, from a service management database, one or more change tickets and one or more incident tickets relating to an information technology infrastructure, defining one or more change-incident pairs based on linkages between the incident tickets and the change tickets, identifying, from the change-incident pairs, one or more dimensions affecting outcomes of implementation of one or more change types, generating at least one recommendation for altering implementation of subsequent changes of a given change type to the information technology infrastructure based on the identified dimensions, applying the at least one recommendation to the implementation of one or more subsequent changes of the given change type to configuration items in the information technology infrastructure, monitoring the information technology infrastructure to determine outcomes of the subsequent changes of the given change type, and modifying the at least one recommendation responsive to the monitoring.
Opening claim text (preview).
The invention claimed is: 1. A method comprising: obtaining, from a service management database, one or more change tickets and one or more incident tickets relating to an information technology infrastructure; defining one or more change-incident pairs based on linkages between the incident tickets and the change tickets; identifying one or more dimensions affecting outcomes of implementation of one or more change types based on the change-incident pairs utilizing a probability tree classifying historical changes to the information technology infrastructure based on: on outcomes of the historical changes to the information technology infrastructure; and the one or more dimensions; generating at least one recommendation for altering implementation of subsequent changes of a given change type to the information technology infrastructure based on the identified dimensions; applying said at least one recommendation to the implementation of one or more subsequent changes of the given change type to configuration items in the information technology infrastructure; monitoring the information technology infrastructure to determine outcomes of the subsequent changes of the given change type; and modifying said at least one recommendation responsive to said monitoring; wherein identifying a given one of the one or more dimensions affecting outcomes of implementation of one or more change types based on the change-incident pairs utilizing the probability tree comprises determining a difference between (i) a first weighting of a first leaf of the probability tree corresponding to negative outcome for one or more changes with a given set of the one or more dimensions and (ii) a second weighting of a second leaf of the probability tree corresponding to a positive outcome for one or more changes with the given set of the one or more dimensions; and wherein the method is performed by at least one processing device coupled to the information technology infrastructure over at least one network. 2. The method of claim 1 wherein the configuration items in the information technology infrastructure comprises one or more servers, databases, middleware, software and business applications. 3. The method of claim 1 wherein monitoring the subsequent changes comprises measuring changes in outcome for the given change type resulting from applying said at least one recommendation. 4. The method of claim 3 wherein modifying said at least one recommendation is based on the measured changes in outcome for the given change type. 5. The method of claim 3 wherein measuring changes in outcome for the given change type comprises checking whether a percentage of changes of the given change type having negative outcomes is reduced. 6. The method of claim 1 wherein identifying the one or more dimensions affecting outcomes of the one or more change types comprises dividing the data into two or more categories based on the outcomes of the historical changes to the information technology infrastructure. 7. The method of claim 6 wherein the two or more categories comprise a first category associated with negative outcomes of the historical changes to the information technology infrastructure and a second category associated with positive outcomes of the historical changes to the information technology infrastructure. 8. The method of claim 7 wherein each of the historical changes is associated with a plurality of dimensions, the plurality of dimensions comprising two or more of: a change type, an owner group, a time, a priority, a configuration item, a risk and an urgency. 9. A computer program product comprising a computer readable storage medium for storing computer readable program code which, when executed, causes a computer: to obtain, from a service management database, one or more change tickets and one or more incident tickets relating to an information technology infrastructure; to define one or more change-incident pairs based on linkages between the incident tickets and the change tickets; to identify one or more dimensions affecting outcomes of implementation of one or more change types based on the change-incident pairs utilizing a probability tree classifying historical changes to the information technology infrastructure based on: on outcomes of the historical changes to the information technology infrastructure; and the one or more dimensions; to generate at least one recommendation for altering implementation of subsequent changes of a given change type to the information technology infrastructure based on the identified dimensions; to apply said at least one recommendation to the implementation of one or more subsequent changes of the given change type to configuration items in the information technology infrastructure; to monitor the information technology infrastructure to determine outcomes of the subsequent changes of the given change type; and to modify said at least one recommendation responsive to said monitoring; wherein identifying a given one of the one or more dimensions affecting outcomes of implementation of one or more change types based on the change-incident pairs utilizing the probability tree comprises determining a difference between (i) a first weighting of a first leaf of the probability tree corresponding to negative outcome for one or more changes with a given set of the one or more dimensions and (ii) a second weighting of a second leaf of the probability tree corresponding to a positive outcome for one or more changes with the given set of the one or more dimensions; and wherein the computer is coupled to the information technology infrastructure over at least one network. 10. The computer program product of claim 9 wherein the configuration items in the information technology infrastructure comprises one or more servers, databases, middleware, software and business applications. 11. The computer program product of claim 9 wherein monitoring the subsequent changes comprises measuring changes in outcome for the given change type resulting from applying said at least one recommendation. 12. The computer program product of claim 11 wherein modifying said at least one recommendation is based on the measured changes in outcome for the given change type. 13. The computer program product of claim 11 wherein measuring changes in outcome for the given change type comprises checking whether a percentage of changes of the given change type having negative outcomes is reduced. 14. The computer program product of claim 9 wherein identifying the one or more dimensions affecting outcomes of the one or more change types comprises dividing the data into two or more categories based on the outcomes of the historical changes to the information technology infrastructure. 15. The computer program product of claim 14 wherein the two or more categories comprise a first category associated with negative outcomes of the historical changes to the information technology infrastructure and a second category associated with positive outcomes of the historical changes to the information technology infrastructure. 16. The computer program product of claim 15 wherein each of the historical changes is associated with a plurality of dimensions, the plurality of dimensions comprising two or more of: a change type, an owner group, a time, a priority, a configuration item, a risk and an urgency. 17. An apparatus comprising: a processing device comprising a processor coupled to a memory; the processing device being configured: to obtain, from a service management database, one or more chang
Probabilistic graphical models, e.g. probabilistic networks · CPC title
Dynamic search techniques; Heuristics; Dynamic trees; Branch-and-bound · CPC title
using ranking · CPC title
Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters · CPC title
characterised by the conditions triggering a change of settings · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.