Requires Free Membership to View
When you register for SearchDisasterRecovery.com, you’ll also receive targeted emails from my team of award-winning editorial writers. As you know, an interruption can threaten your organization at any time – and it’s our goal to ensure you’re armed with the right tips and information to help you ensure a swift recovery.
Rich Castagna, Editorial DirectorThis table lists the basic categories and actions you need to manage your change control process and track changes in your environment.
Category |
Action |
Application name |
Enter both the application name and any technical name of the application. |
Dependency (Input) |
Enter this if the application requires some input from another application or is dependent upon another application. |
Dependency (Output) |
Enter for tracking purposes if this application is a dependency for another application. |
Operational platform |
Enter whether the application executes on a mainframe, server or PC. Also add the OS used, with details of the version and release date. |
Used by |
Name the departments using the application. |
Latest production version |
Add information about the current production version. |
Latest test version |
Add information regarding the latest version being tested. |
Last changed by |
Enter contact information for person who made the last change to the production version. |
Reason for change |
Detail the reason for the latest change to the operating environment. |
Additional comments |
Add any additional or relevant information to this entry. |
You can also add more categories if they are applicable to your IT environment, but make sure you have a history of changes accessible as well. Whether you choose a change management tool or create your own spreadsheet, it's important to document the changes to data storage environment and make sure everything is current.
This was first published in June 2010