This policy and procedure has been established to ensure that in the event of a disaster or crisis, personnel will have a clear understanding of who should be contacted.
The person who initially discovers the incident or problem will contact:
IT Dept. at 413-499-0607 between the hours of 7:30 am – 5:30 pm or 413-266-1124 outside of regular business hours.
When an incident occurs all IS staff must be informed. The Director of Information Services will then decide the extent to which the DRP must be invoked. Responsibilities of the Directopr of Information Services are to:
• Respond to a potential disaster;
• Assess the extent of the disaster and its impact on the business, data center, etc.;
• Decide which elements of the DR Plan should be activated;
• Maintain vital services and return to normal operation;
• Ensure employees are notified and allocate responsibilities and activities as required.
• Restore key services within 4.0 business hours of the incident;
• Recover to business as usual within 8.0 to 24.0 hours after the incident
Key trigger issues at headquarters that would lead to activation of the Data recovery Plan are:
• Total loss of all communications
• Total loss of power
• Flooding of the premises
• Loss of the building
There are many potential disruptive threats which can occur at any time and affect the normal business process. We have considered a wide range of potential threats and the results of our deliberations are included in this section. Each potential environmental disaster or emergency situation has been examined. The focus here is on the level of business disruption which could arise from each type of disaster.
Potential disasters and recovery methods have been assessed as follows:
| Potential Disaster | Remedial Action(s) |
|---|---|
| Flood | All hardware on relay racks- All hardware on grade level surface except BSITU, HC and HP |
| Tornado | Move hardware from alternative sites and restore AD when connectivity is available |
| Electrical Storms | Monitor Network for alerts. Isolate any failed hardware. Replace hardware if necessary. |
| Act of Sabotage | Monitor Network for alerts. Isolate any failed hardware. Replace hardware if necessary. |
| Electrical Power Failure | All racks tied into emergency generators and linked to UPS systems for soft shutdowns. generators tested weekly |
| Loss of network services | Test Internet connectivity on Firewall X7 interface. Contact Haas monitoring service, then Cornerstone Telco |
Key business processes and the agreed backup strategy for each are listed below. The strategy chosen is for an offsite backup through the Vault Logics company. This strategy entails the maintenance of full daily backups of mission critical data and the backup site(s). Each campus has two domain controllers all running within the same active directory forest. This way even if both fail there is no data stored only on the servers that cannot be recovered from another.
PLAN DOCUMENTATION STORAGE
Hard copies of this plan will be stored in the data center/computer closet of all sites. Each member of the IS Department will be issues hard copy of this plan. The plan will be reviewed yearly with all IS staff during the month of June. A master protected copy will be stored on the Policies & Procedures website.
The principal objective of the disaster recovery program is to develop, test and document a well-structured and easily understood plan which will help the company recover as quickly and effectively as possible from an unforeseen disaster or emergency which interrupts information systems and business operations. Additional objectives include the following:
• The need to ensure that all employees fully understand their duties in implementing such a plan
• The need to ensure that operational policies are adhered to within all planned activities
• The need to ensure that proposed contingency arrangements are cost-effective
• The need to consider implications on other company sites
• Disaster recovery capabilities as applicable to key customers, vendors and others
STATEMENT OF INTENT
This document delineates our policies and procedures for technology disaster recovery, as well as our process-level plans for recovering critical technology platforms and the telecommunications infrastructure. This document summarizes our recommended procedures. In the event of an actual emergency situation, modifications to this document may be made to ensure physical safety of our people, our systems, and our data.
Our mission is to ensure information system uptime, data integrity and availability, and business continuity.
The time and date of the order for involuntary anti-psychotic medication administration must be documented on the doctor’s order sheet by the physician, or documented by a licensed nurse as a telephone order from the physician. The use of medication will be documented in the student’s case record with at least the following information:
a) A description of the precipitating incident or series of incidents, the alternative interventions attempted including all efforts to prevent the use of chemical restraint, and the reasons the medication was necessary.
b) The fact that involuntary medication was the least restrictive alternative and why.
c) The time and from whom the order for administration was obtained, and the names and titles of all other persons notified and/or involved in the decision.
On the day new orders are received, the nurse must enter a progress note in the student’s chart that explains the new order and the reasons for the change. When a verbal consent from a family guardian/agency guardian is received, it must be recorded on the consent form with a signature from two nurses and also in a progress note in the student’s chart.