DePaulinformation services
Technology Contact Center|IS home|IS Forms|Campus Connection|Contact Us




Security
Information Security

Business Continuity


Systems Data Information & AccessCommunication ServicesComputers on CampusAre you new to DePaul?Resources & ReferencesAbout Information Services






Business Continuity
More on Business Continuity:
Business Continuity Terms

Planning Tips

DR Software

Additional Information

News & Updates

DR Software

Living Disaster Recovery Planning Software (LDRPS) is a system that stores disaster recovery plans. IS is the administrator of LDRPS; so if a department wants to implement it, contact the BC Team.

LDRPS TIP SHEET

Modifications can be made to the system screens, reports and table of contents. Please notify the BC Team if you feel a software customization would enhance your plan(s).

Plans can be entered using the Plan Assistant as a guide or through the use of the menu. The subsequent tips are sequenced in the same order that the Plan Assistant follows.

Overview
  • Use the Overview section on the plan menu page to enter a general department summary. At a minimum, include reference to the person (and the names of their alternates) who is responsible for initiating the DR plan for the department.

Employee Attributes
  • Feel free to create new attributes that are meaningful for your department. These attributes should represent skills or traits that may be of importance during an emergency or during the recovery period.

  • It is suggested that you provide the list of attributes to each employee and have them check off the ones that pertain to them. Use the completed surveys as basis for data entry.

Call Lists
  • You may create multiple call lists for each department.

  • Make sure you have addressed an inability to reach a person on the phone list so that the call list chain is not broken; i.e. who will place the calls to the individuals below that person?

  • Make sure there is at least one means of contacting a person. Multiple means of contacting an individual are strongly recommended.

Vendors
  • Limit your vendor list to critical or specialty vendors.

  • Identify at least one vendor representative for each vendor.

  • The Vendor Representatives report will not print any vendors for which there is no associated representative.

Critical Contacts
  • Examples of critical contacts are critical internal DePaul contacts, local authority emergency numbers, landlords, etc. Do not list vendors or departmental staff members as critical contacts (these should be identified in the screens above).

  • The Critical Contact Representatives report will not print any critical contacts for which there is no associated representative.

Teams
  • At a minimum, identify teams that are responsible for disaster recovery planning and testing, emergency response, and recovery efforts.

  • You may also wish to use the Teams screen to identify teams that handle departmental daily processes. This might prove useful after an emergency to quickly assemble those individuals who are key to critical business processes.

Software
  • Omit references to any general university network-supported software (i.e. GroupWise, Word, Excel, Power Point, browsers).

  • Do refer to any specialized software that is particular to your business operations.

Equipment
  • List all equipment required to recover your business operations. The Equipment Required Over Time section should represent quantities needed for minimum survival needs, not business as usual requirements.

  • Be sure to include any servers that host any applications unique to your area.

Supplies
  • Limit supplies to specialized items needed for a particular process. Omit standard, easy-to-acquire supplies such as paper, pens, staplers, etc.

Vital Records
  • Indicate critical documents to your business operations. If the document is not backed up or stored in an alternate location, this may be a reminder to do so. Examples of critical documents may be lease agreements, insurance policies, tax records, etc.

Processes
  • Define each process that enables your department to deliver its product or services.

  • You may also wish to establish processes that are related to disaster recovery; for example, the process to recover lost data, process to acquire alternate working space, etc.

  • There is a sub-menu (the Assignments button) where you can identify software, supplies, equipment, vital records, and teams that are associated with a particular process.

Documents
  • Make sure documents are embedded, not linked (the Linked File check box should be unchecked).

  • In order for a document to be listed under your plan's Table of Contents and print as a consolidated report, the document must be given an appendix number. The suggested sequence is: A., B., C.

  • For presentation purposes, you may wish to identify the appendix number directly on the source document (for example, as a header or footer).


PRINTING PLANS

There are two menu items that enable you to print plans:

  1. Print Plans
    • You can print your plans without appendix items (handy if you have multiple or lengthy appendices) by deactivating the Add Appendices for Each Plan checkbox.

    • If you would like to incorporate a document in the body of the main report instead of as an appendix item, we can create a special Table of Contents for your department that accomplishes this. When printing the report, you can refer to this table of contents in lieu of the default documents.

  2. Manage Reports
    • Use Manage Reports to print a single report. The report can be one that is considered a default on your Table of Contents or one of the numerous other reports that come pre-delivered with LDRPS.



© 2001-2004 | DePaul University | Disclaimer | Webmaster
1 E. Jackson Chicago IL 60604 | 312-362-8000