Change Record Request system (CRRS)

This is the synopsis of Change Record Request System (CRRS) which is part of the Change Record Management System (CRMS) suite that I am working on. It provides a means for information systems analysts to seek approval from a supervisor or a manager before downing an ailing server or other critical network objects. This is different from when a server or network object goes down abruptly as a result of hardware or software problem and a trouble ticket is generated. Rather it is when an analyst observes an abnormality in the course of operation of a server and decides to perform a maintenance work on the server in order to avoid crash, loss of data and prolonged downtime.

CRRS provides the analyst the means and interface to do the following:

·         Report the problem to superiors with problem description

·         Give estimated hours / minutes of downtime

·         Establish a paper trail to show that the superiors were duly notified before downing a critical network object. In other words, CRRS serves as a security for the analyst. This is because with the approval of the supervisor or manager, the whole blame due to prolonged downtime as a result of unforeseen circumstances during maintenance will not be on the analyst alone.

CRRS affords the supervisor and the manager the opportunity to evaluate the problem in terms of impact on users and business processes and then make recommendation to the analyst on the best day and time to perform the maintenance work.

CRRS is comprised of three form interfaces which include: Change record request form, decision form and maintenance completion notification form.