Expert Advice Community

Guest

Incident and Change Management in two separate SW tools?

  Quote
Guest
Guest user Created:   Jul 08, 2016 Last commented:   Jul 08, 2016

Incident and Change Management in two separate SW tools?

I wanted to get better understanding about incident and change management. How bad is to separate solution and processes? For example Incident and Service Requests register in on solution and for example changes or bugs for product in other software. How bad is it and what are the risks?
0 0

Assign topic to the user

ITIL® & ISO 20000 PREMIUM DOCUMENTATION TOOLKIT

Step-by-step implementation for smaller companies.

ITIL® & ISO 20000 PREMIUM DOCUMENTATION TOOLKIT

Step-by-step implementation for smaller companies.

Expert
Branimir Valentic Jul 08, 2016

Answer:
Generally, I would suggest to keep all processes in one tool i.e. that you manage all processes with single SW solution. Reason for that is that you will have all information in one place and many information will be transferred automatically between process activities (e.g. you enter only once information in Incident Management and them when you open a Problem ticket or Change request - same data will be transferred). If you don't have that (you asked for risks) - then there is a chance that some information will be lost (e.g. asset information which you need for Incident management as well as Change Management).
Quote
0 0

Comment as guest or Sign in

HTML tags are not allowed

Jul 08, 2016

Jul 08, 2016

Suggested Topics

Guest user Created:   Aug 30, 2022 ITIL & ISO 20000
Replies: 1
0 0

ITMS Process

Guest user Created:   Aug 08, 2022 ITIL & ISO 20000
Replies: 1
0 0

Valor y entregables de ITIL