Phoenix Small Business Edition Software

PHOENIX DISASTER RECOVERY PLANNING SYSTEM SOFTWARE:
SMALL BUSINESS EDITION
By Binomial International

Ideal for the smaller business with a single location. Output of the plan to RTF, then can also
be saved to PDF or Web.

The Phoenix Disaster Recovery Planning software program is a network enabled, multi-user,
collaboration tool. It provides the capability to generate, house and maintain a comprehensive
Business Continuity Plan. The ideal BCP creation and management tool for the medium to
large enterprise.

The software will create a complete Business Continuity and Disaster Recovery Plan by
assisting you in the selection of planning content and in the generation of a fully formatted
document. It will house the plan in software format for continuous maintenance. It is has
multi-user capabilities and acts as a cross departmental collaboration tool, allowing multiple
users to contribute to the development of the overall plan.

- Easy generation of the Information required in Business Recovery Plans
- Easy to revise and maintain your plan
- When combined with training reduces Business Recovery Plan development time by over
75% and saves you thousands of dollars.

All businesses depend heavily upon information and the ability to process and analyze this
information. These businesses increasingly depend on computer- supported information
processing and telecommunications. Technology and automated systems are often used to
process and analyze information and their disruption for even a few days could cause severe
financial loss and threaten the very survival of the business. This dependency will continue to
grow with the trend toward decentralizing information technology to individual organizations
within companies. The increasing dependency on computers and telecommunications for
operational support poses the risk that a lengthy loss of these capabilities could seriously
affect the overall performance of the company.

A business recovery plan gives your company a competitive advantage.

PHOENIX is a menu driven system in Windows that helps you to produce a Business
Recovery Plan for your company.

You decide which topics to include in your Plan and which databases to include and Phoenix
will do the rest. It is an automated system, which will quickly and easily generate the
components of your Recovery Plan.

After you have created the plan, Phoenix is used to continue to maintain the plan, through
modifying text and updating data.

- - - - - -

PROCEDURES MODULE

The Phoenix Procedures Module contains textual information for inclusion in the recovery
system. The first section is information on background, recovery planning and a sample plan
format. The second section shows all of the teams that could be a part of the plan and the
tasks that each team will perform, before, during and after a disaster.

- - - - - -


TEAMS MODULE
The Phoenix Teams Module contains textual information for inclusion in the recovery system.
The first section is information on background, recovery planning and a sample plan format.
The second section shows all of the teams that could be a part of the plan and the tasks that
each team will perform, before, during and after a disaster.

- - - - - -

DATABASES MODULE

This module provides Phoenix users with a facility to enter, update and report data related to
their Disaster Recovery Plan using a set of pre-defined tables.

Using pre-defined tables means that the user is not required to know anything about
database structures or design to use this product. The user only has to select the table to be
updated and enter their data.

The Phoenix Database module maintains information on assets that you will need to effect an
orderly recovery from any loss. There are eighteen tables:

Hardware
Critical Functions
Software
Building Plans
Other assets
Insurance Policies
Suppliers
Hotsites
Systems
Salvage
Customers
Equipment
Applications
Vital Information
Personnel
Telephone
Teams
Company Records
Skills

The Databases window is used to track information necessary when recovering from a
disaster. Having everything in one place will make it easier to pick up the pieces.

- - - - - -

ASSEMBLY MODULE

On completion of working through the three main system modules, a few simple clicks
generate your complete Disaster Recovery Plan in a few minutes. It can then be printed or
exported for access through a word processor – simple fast and effective.

= = = = = = =

The objectives for having a Plan documented, tested, and ready for immediate use are to:
- limit Financial losses and hardships
- minimize the extent of interruption
- define service alternatives for accomplishing critical applications
- ensure controlled emergency recovery
- regain total processing capability
- provide trained personnel to handle emergency conditions and recovery operations
- define policies which will minimize the recovery time and cost.

Recovery time is directly related to the availability of plans. Where plans exist, recovery takes
days, or at most, a few weeks; where plans do not exist, recovery can take months, years, or
even be impossible.

The real benefits of a plan are minimizing potential loss by identifying, prioritizing and
safeguarding those assets that need the most protection. The plan will save valuable time and
money in the event of a disaster.

Phoenix SBE is a standardized and proven methodology which guides you to quickly produce
your plans. There are two modules in the Phoenix SBE Disaster Recovery Planning System,
Procedures and Databases.

= = = = = = =

Following is a listing of the contents of this package. This will generate a plan of about
200 pages.

PROCEDURE MODULE - CONTENTS

The following is the table of contents for a complete run of the Phoenix Disaster Recovery
Planning Procedures Module. When you buy this system, the textual information for each of
these topics is complete. These are not program stubs but rather the full text of the
information that you need to organize your Plan.

1.0 INTRODUCTION TO BUSINESS RESUMPTION PLANNING
1.1 Recovery Objectives
1.2 Situation Report

2.0 PROJECT BACKGROUND
2.1 Project Background
2.2 Project Scope
2.3 Project Objectives

3.0 EVENTS AND SITUATIONS TO BE CONSIDERED
3.1 Location Hazards
Proximity To Airport
Proximity to Chemical Factory
Proximity to Natural Gas
Proximity to Railway
Low-lying Area
Sea
High-rise Building
Congested Area
Proximity to Military Exercise Area
Adequacy of Fire Protection
Industrial Parks
Major Construction Equipment
3.2 Possible Exposures specific for COMPANY
3.3 Possible Disasters:
3.4 Preventive Measures In Place:
3.5 Analysis by Possible Disaster
Location Hazards
High Rise Buildings
Congested Area
Responsiveness of Fire Protection Services
Fire
Water/Flood
Smoke
System Contamination
Employee Sabotage
Intrusion of Unauthorized Personnel
Hardware Failure
Software Failure
Loss of Key Personnel
Negative Public Relations

4.0 PROTECTION, PREVENTION AND RESUMPTION
4.1 Personnel Security
4.2 Physical Security
4.3 Fire Protection
4.4 Electrical Systems

5.0 TEAM STRUCTURES AND RESPONSIBILITIES
5.1 The Recovery Teams
5.1.1 Resumption Management Team
5.1.2 Computer Teams
Mainframe Hardware Team
Mainframe Software Team
Mainframe Operations Team
Mini-computer Hardware Team
Mini-computer Software Team
Mini-computer Operations Team
Data File Off-site Storage Retrieval Team
Personal Computer Restoration Team
Communication (Data) Restoration Team
5.1.3 Service Teams
Administration Team
Transportation Team
Records Management Team
Supplies Team
Facilities Team
Voice Communications Restoration Team
Transition Team
5.1.4 Salvage Teams
Damage Assessment Team
Facilities Salvage Teams
Records Salvage Team

6.0 TEAM ACTIVITIES AND RESPONSIBILITIES
6.1 Pre-Disaster Team Activities
6.1.1 Resumption Management Team
6.1.2 Computer Teams
Mainframe Hardware Team
Mainframe Software Team
Mainframe Operations Team
Mini-computer Hardware Team
Mini-computer Software Team
Mini-computer Operations Team
Data File Offsite Storage Retrieval Team
Personal Computer Restoration Team
Data Communications Restoration Team
6.1.3 Service Teams
Administration Team
Transportation Team
Records Management and Salvage Team
Supplies Team
Relocation (Facilities) Team
Voice Communications Team
Transition Team
6.1.4 Salvage Teams
Damage Assessment Team
Facilities Salvage Team
Records Salvage Team
6.2 Team Activities During a Disaster
6.2.1 Resumption Management Team
6.2.2 Computer Teams
Mainframe Hardware Team
Mainframe Software Team
Mainframe Operations Team
Mini-computer Hardware Team
Mini-computer Software Team
Mini-computer Operations Team
Data File Offsite Storage Retrieval Team
Personal Computer Restoration Team
Data Communications Restoration Team
6.2.3 Service Teams
Administration Team
Transportation Team
Records Management and Salvage Team
Supplies Team
Facilities Team
Voice Communications Restoration Team
Transition Team
6.3 Post-Disaster Team Activities
6.3.1 Resumption Management Team
6.3.2 Computer Teams
Mainframe Hardware Team
Mainframe Software Team
Mainframe Operations Team
Mini-computer Hardware Team
Mini-computer Software Team
Mini-computer Operations Team
Data File Offsite Storage Retrieval Team
Personal Computer Restoration Team
Data Communications Restoration Team
6.3.3 Service Teams
Administration Team
Transportation Team
Records Management and Salvage Team
Supplies Team
Facilities Team
Voice Communications Restoration Team
Transition Team
6.3.4 Salvage Teams
Damage Assessment Team
Facilities Salvage Team
Records Salvage Team

7.0 VALIDATION
7.1 Testing the Plan
7.2 Training Personnel to Use the Plan

8.0 MAINTENANCE OF THE PLAN

= = = = = = =

DATABASE MODULE CONTENTS

In addition to having procedures in your recovery plan, you also need to know what assets
you had before a disaster occurs. Phoenix Databases help you to keep accurate account of
these assets. The Phoenix Databases include the following:

Hardware
Make - name of the manufacturer of the hardware
Model - model name of the hardware
Quantity - quantity of the hardware
Unit Cost - cost per unit of the hardware
Location - location of the hardware
Replacement Make - this is the make of the hardware that you would replace this hardware
with. It may be the same or it may be an updated version
Replacement Model - this is the model of the hardware that you would replace this hardware
with. It may be the same or it may be an updated version
Serial Number

Software
Name - name of the software
Version - version of the software
Manufacturer
Quantity - quantity of the software
Unit Cost - cost per unit of the software
Location - location of the software
Backup Location - this is the location of the backup copies of this software
Serial Number

Systems
Name - name of the system
Platform
Responsibility
Location - location of the system
Backup Location - this is the location of the backup copies of this system
Backup Freq - this is the frequency of the backups

Applications
Name - name of the application
Platform
Responsibility
Location - location of the application
Backup Location - this is the location of the backup copies of this application
Backup Freq - this is the frequency of the backups

Other Assets
Name - name of the asset
Code - inventory control code
Description
Location - location of the asset
Quantity - quantity of the asset
Original Price
Present Value
Replacement Cost
Serial Number

Suppliers
Code - supplier control code
Company Name - name of supplier
Address
Day Contact - this is the name of person to talk to during the day
Day Phone
Night Contact - this is the name of person to talk to during the night
Night Phone
Fax

Teams
Code code number for this team
Name name of the team

People
Employee Number
Name - name of the employee
Team - team of which this employee is a member
Position - position held on this team
Work Telephone
Home Telephone
Department - normal department in the company
Skill # - skills which this employee has

Skills
Code code number for this skill
Name name of the skill

Emergency Telephone List
Title - name or title of person to be contacted
Emergency - telephone number to be used in an emergency
Non-emergency - telephone number to be used for normal use

Customers
Identification Number
Company
Address
Day Contact - this is the name of person to talk to during the day
Day Phone
Night Contact - this is the name of person to talk to during the night
Night Phone
Fax

= = = = = = =
Phoenix SBE comes with one year of FREE support by toll-tree telephone and email.
Also included during this year are free software upgrades. Annual support is 15% of the
purchase price (after the first year).

= = = = = = =

ALSO AVAILABLE: See DR657 for even MORE powerful features and functions, including
Internet, Intranet Client/Server and multi-user options!

CORPORATE EDITION (CE)
The ideal BCP creation and management tool for the medium to large enterprise with
multiple

PHOENIX FOR INTERNET SERVICE PROVIDERS (ISP)
The ideal BCP creation and management tool for any Internet Service Provider. Output of
the plan to RTF, then to PDF or Web.

PHOENIX FOR DATA CENTERS (DC)
The ideal BCP creation and management tool for any Data Center or Internet Data Center.
Output of the plan to RTF, then to PDF or Web.


PHOENIX FOR BANKS
The ideal BCP creation and management tool for Banks of all types and sizes. Output of
the plan to RTF, then to PDF or Web.


PHOENIX FOR CREDIT UNIONS (CU)
The ideal BCP creation and management tool for Credit Unions of all sizes. Output of the
plan to RTF, then to PDF or Web.

= = = = = = = = = =

PHOENIX SMALL BUSINESS EDITION
Order#DR-300, (Single-User, Windows Version)

= = = = = = = = = =

4 Arapaho Rd.

Brookfield, CT 06804-3104 USA

1-888-ROTHSTEin; (888.768.4783)

Telephone: 203.740.7444; 888.768.4783

Fax: 203.740.7401

"Keep Me Posted" Business Survival Newsletter