X hits on this document

Word document

DRAFT Princeton University Continuity of Operations Plan (COOP) - page 9 / 17





9 / 17

Continuation of Business

State the business functions and processes of the application, ranked by priority, from highest to lowest, in the following categories. For each, describe how these functions will continue to be performed after a disaster and the system is down (manually, via pc software, etc.) as well as how data will be put into the system, and how processing will be affected, once it is back up again.  Plan for outage periods of less than a week, one to three weeks, and four to eight weeks.  Specify the volume of data projected for each time range.  If a process’ category is effected by the period of system unavailability, list the process in the highest category, and indicate the lower values in the table cell for that period. Also note if the criticality is different during different business cycles, e.g. month end, year end, etc.  For each period estimate how long it will take to completely catch up, and have processing return to normal.


Process Name

Less Than One Week

One to Three Weeks

Four To Eight Weeks

Example 1: Transcript Request

Sys Down

Suspendable Average of 5 transcripts a day

Produce from Datamall Average of 25 transcripts a week

Produce from Datamall, and send disclaimer regarding currency of data Average of 25 transcripts a week

Sys Up

No specific action taken, return to normal processing of requests as they come in

Example 2: Create PO

Sys Down

If down for more than 3 hours, begin generating manual PO numbers, and process with PC backup sustem Do not bother preserving the data, as it will not be entered into system when it is back up. These POs will permanently be tracked on paper.  Approximately 30 to 50 POs are generated each hour.

Sys Up

Return to normal processing, continue tracking contingency POs until all are closed and reconciled. All contingency POs should have cleared the system in 90 days.

Example 3: Billing Cycle

Sys Down


Process Bills by hand and mail, preserve data to enter into system when it is back up. Approximately 2,000 bills are generated each month.

Sys Up

Normal business process.  It is acceptable for the bills to be a week late.

Enter the latent data into the system with the correct date, tag as already billed. Resume normal business process for bills thereafter.  Allow 2 days of data entry per week down to enter all the data into the system, and resume normal processing.

Document info
Document views21
Page views21
Page last viewedFri Oct 21 19:13:54 UTC 2016