Creating a new Change request

The change request form comprises three sections. The fields in all sections are compulsary, if you omit any of the fields the change request will not be saved.

The first section is a summary of the change you intend to occur. This is a brief description, the maximum outage, what services will be affected, what change implementation group you expect to perform the change and who will be testing it. You must also of course provide the date and time you would like the change to be performed.

The second section is for charging. No change will be accepted unless it relates to an existing problem record, or unless a chargable work request number is provided. The business unit that owns the application must also be provided.
Note that if a problem record is used as justification the change record must be for something simple, like stopping and restarting the application or turning on tracing. If for example the change is to apply a new version of the application to fix a problem that is not considered a problem fix, but a new chargeable request. As such if you only provide a problem number your change would be rejected. Bearing that in mind try to use a changeable reference in all you change requests.

The third field is to describe in detail the actions to be taken by the change implementation group to perform the change. The details must be clear enough that someone who does not understand your application or environment can perform the change. If the change implementation group believes the instructions are unclear the change will be rejected.
Note that while the change is in draft you may continue to add new blocks of instructions to the change request, so don't worry if the field seems to small; just save as draft then update it to add additional text.