Recovery of data and data processes
One embodiment of a data recovery management system includes prompt logic operable to prompt a user to provide information describing impact that an extended interruption of a project tracking system would have on an work unit that uses the project tracking system to perform a particular workflow process; a database coupled to the prompt logic, operable to store feedback received from the user in response to answering questions proposed by the prompt logic; and organizational logic operable to compile information stored in the database for each work unit that utilizes the project tracking system to perform a particular workflow process. Other systems and methods are also provided.
1. A data recovery management system, comprising:
prompt logic operable to prompt a user to provide information describing impact that an extended interruption of a project tracking system would have on an work unit that uses the project tracking system to perform a particular workflow process;
a database coupled to the prompt logic, operable to store feedback received from the user in response to answering questions proposed by the prompt logic; and
organizational logic operable to compile information stored in the database for each work unit that utilizes the project tracking system to perform a particular workflow process.
2. The system of claim 1 , further comprising:
secondary prompt logic operable to prompt the user to provide information describing steps to be taken for performing a particular workflow process if the project tracking system is inoperable for an extended period of time.
3. The system of claim 2 , wherein the secondary prompt logic prompts for identification of data fields that coincide with types of information that the project tracking system tracks in normal operation of the particular workflow process.
4. The system of claim 1 , wherein the prompt logic prompts for a categorization of the particular function in terms of a length of time that the function can be disrupted without having to implement a contingency plan.
5. The system of claim 1 , wherein the prompt logic prompts for a categorization of the particular function in terms of a level of dependency of the particular function on availability of the project tracking system.
6. The system of claim 1 , wherein the prompt logic prompts for a characterization of revenue losses that would be experienced if the particular function were not performed during an extended disruption of the project tracking system.
7. The system of claim 6 , wherein the characterization of revenue is queried in terms of different periods of time.
8. A method for managing recovery of data and data processes, comprising:
prompting a user to provide information describing impact that an extended interruption of a project tracking system would have on an work unit that uses the project tracking system to perform a particular workflow process;
storing feedback received from the user; and
compiling information stored in a database for each work unit that utilizes the project tracking system to perform a particular workflow process.
9. The method of claim 8 , further comprising:
prompting the user to provide information describing steps to be taken for performing a particular workflow process if the project tracking system is inoperable for an extended period of time.
10. The method of claim 9 , further comprising:
prompting for identification of data fields that coincide with types of information that the project tracking system tracks in normal operation of the particular workflow process.
11. The method of claim 8 , further comprising:
prompting for a categorization of the particular function in terms of a length of time that the function can be disrupted without having to implement a contingency plan.
12. The method of claim 8 , further comprising:
prompting for a categorization of the particular function in terms of a level of dependency of the particular function on availability of the project tracking system.
13. The method of claim 8 , further comprising:
prompting for a characterization of revenue losses that would be experienced if the particular function were not performed during an extended disruption of the project tracking system.
14. The method of claim 8 , wherein the characterization of revenue is queried in terms of different periods of time.
15. A computer readable storage medium having a program for managing recovery of data and data processes, the program having instructions for performing:
prompting a user to provide information describing impact that an extended interruption of a project tracking system would have on an work unit that uses the project tracking system to perform a particular workflow process;
storing feedback received from the user; and
compiling information stored in the database for each work unit that utilizes the project tracking system to perform a particular workflow process.
16. The computer readable storage medium of claim 15 , the program further performing:
prompting the user to provide information describing steps to be taken for performing a particular workflow process if the project tracking system is inoperable for an extended period of time.
17. The computer readable storage medium of claim 15 , the program further performing:
prompting for identification of data fields that coincide with types of information that the project tracking system tracks in normal operation of the particular workflow process.
18. The computer readable storage medium of claim 15 , the program further performing:
prompting for a categorization of the particular function in terms of a length of time that the function can be disrupted without having to implement a contingency plan.
19. The computer readable storage medium of claim 15 , the program further performing:
prompting for a categorization of the particular function in terms of a level of dependency of the particular function on availability of the project tracking system.
20. The computer readable storage medium of claim 15 , the program further performing:
prompting for a characterization of revenue losses that would be experienced if the particular function were not performed during an extended disruption of the project tracking system.