Business Continuity Policy Statement
Â
Purpose
The main purpose of the business continuity policy is to prepare SanGrafix for any kind of threat. Business continuity policy is just another term for backup. Running a company without backup is not a smart move in business industry. Our business continuity plan should contain a comprehensive roadmap to restore any information during any disaster. Copies of the plan should be sent out to all important personals so that the services are never threatened, and it should present complete analysis of all the possible threats to the company. Company should response to the threat because of both type of threat and extent of the threat. All SanGrafix sites and online storages are expected to implement preventive measures to minimize network failure (Shinder, 2017).
Scope
The scope of this plan is limited to manage both locations of SanGrafix in the best possible way and to provide the best service and most reliable form to all customers.
Plan Objectives
- Will provide a guide for the SanGrafix recovery teams.
- Provides procedures and resources needed to assist in recovery.
- This will identify customers that must be notified in the event of a disaster.
- This assists in avoiding confusion experienced during a crisis by documenting, testing and reviewing recovery procedures and maintain a sound connection between both the locations
- This will identify alternatives for supplies, resources.
Assumptions
Each support organization is liable to have its own different and unique plan for recovery procedures and critical resource information.
Disaster definition
Any kind of loss in utility service such as water and power, connectivity between the systems of SanGrafix, or any kind of natural disaster that causes an interruption in the service, provided by SanGrafix operations.
Recovery teams
- Emergency Management Team (EMT)
- Location Response Coordinator (LRC)
- Technical Services Engineering (TSE)
Team member responsibilities
- All the members should keep an updated contact list of all the concerned staff members
- Â Â All team members should read this file at least once so they know the contents of this file
Data backup policy
Full backups system should be available for the files and software that are irreplaceable or have a high replacement cost. Backup material should be stored in a secure and a completely separate location from both the locations of SanGrafix.
Following is the basic key for its data backup and archiving:
Files retention policy
Backup material should be stored in a secure and a completely separate location from both the locations of SanGrafix.
Billing files
Tapes greater than four years old are destroyed every year months.
Tapes less than three years old must be stored locally offsite.
System software files
A copy of the most current updates files must be every week.
Offsite backup is also necessary.
Procedures for emergency management
The following procedures are to be followed by system operations personnel and other designated personnel in the event of an emergency. Where uncertainty exists, the more reactive action should be followed to provide maximum protection and personnel safety.
In the event of any situation where access to a building housing a system is denied, personnel should report to alternate locations. Primary and secondary locations are listed below.
Alternate locations
Workplace: San Francisco
Try to contact your immediate supervisor or management
Workplace: SunnyvaleÂ
Try to contact your immediate supervisor or management
In the event of a natural disaster
In the event of a major catastrophe affecting a SanGrafix facility, immediately notify the managerial department
Notify Regional Technical Manager of pending event,
Transfer portable generators with fuel within 100 miles.
Deploy support personnel, tower crews, and engineering within 100 miles.
Thing you require for the deploy plan
Create an image of the system and files
Back up critical system elements
Verify backup generator fuel status and operation
Create backups of e-mail, file servers, etc.
Fuel vehicles and emergency trailers
In the event of a fire
In the event of fire or smoke in any of the facilities, the guidelines are provided below that should be followed:
If fire or smoke is present in the facility, evaluate the situation and determine the severity, categorize the fire as Major or Minor and take the appropriate action as defined in this section. Call 911 as soon as possible if the situation warrants it.
Persons need to attempt to put out minor fires (e.g., single hardware component or paper fires) by making use of hand-held fire extinguishers located all through the facility. Any other fire or smoke situation will be handled by experienced building workers until the local fire department arrives.
In case of a major fire, call 911 and immediately and leave the area.
In case of any emergency situation, system site security and individual safety are the major things to consider.
In case of a major catastrophe affecting the facility, notify the Regional Technical Manager immediately.(“Business Continuity Plan”).
In the event of a network services provider outage
Procedure
If outage will be greater than half hour, direct all calls via microwave or other service to alternate location in Sunnydale. If outage is major and in case all networks are down and downtime will be greater than 12 hours, organize satellite equipment, if available.
In the event of a hack attempt to the system
Shut down all the system to avoid any loss and contact headquarters.
Notification of incident affecting the site
On-duty personnel responsibilities
In office hours:
Upon observation or notification of a potentially serious situation use proper evacuation methods and notify the Location Response Coordinator.
If out of hours:
Technical Services providers should contact the Location Response Coordinator (Shinder, 2017).
Inform team members of decision
If a disaster is not declared, the team of location response will continue to address as well as manage the situation and will provide regular updates to EMT.
the EMT.
If a disaster is declared, the Location Response Coordinator will notify the Incident Response Team members immediately for deployment.
Declare a disaster if the situation cannot be fixed within the predefined time frames. The authorized person will declare a disaster and a backup is vital who is also authorized or declaring a disaster if primary person is not available.
Operations recovered
Assuming all related operations have been recovered to an alternative site, and employees are supposed to support the operations, the company can announce that it is operating in a normal manner at the recovery location (Shinder, 2017).
SanGrafix recovery teams
Emergency management team (EMT)
Responsibilities:
Organization must be responsible for overall management of the disaster recovery effort, evaluation and determining disaster declaration, and communications with senior management
They should evaluate which recovery actions should be invoked and activate the corresponding recovery teams. They should provide senior management with ongoing status information
Acts as a communication channel to corporate teams and major customers
Work with vendors and IRT to develop a rebuild/repair schedule
Location Response Coordinator (LRC).
Support activities:
Notify the Incident Recovery Team
- Gather harm assessment info and report it to EMT
ï‚· Determine recovery wants.
Command center and connected operations musts be established. Command center can be a organized meeting facility wherever EMT/LRT/IRT members meet to organize harm assessment and business recovery tasks for the affected operations.
Notify all Team Leaders and advise them to activate their arrange (s) if applicable, primarily based upon the disaster scenario. If no disaster is asserted, then take applicable action to come to traditional operation victimization regular employees.
Determine if vendors or different groups are required to help with elaborate harm assessment.
•Prepare post-disaster interrogation report
•Coordinate the event of website specific recovery plans and guarantee they’re updated semi-annually.
Location Response Team (LRT)
Charter:
The Location Response Team (LRT) is accountable for the early alerting/notification of the issue to the LRC during normal business hours. In case of off hours, the LRT will be notified as well as LRC. In case of a disaster announcement, this team will become a part of the Incident Response Team.
Support activities:
Provide the subsequent data to the LRC within the event of Associate in Nursing outage:
a. form of event
b. Location of incidence
c. Time of incidence
Coordinate commencement of voice and knowledge communications:
a. Work with management to re-route voice and knowledge lines, particularly once alternate
Web site (s) or alternate work locations square measure predefined
b. Recover voice mail and email correspondence systems once requested by EMT.
c. Verify voice mail and email correspondence square measure operational at the alternate web site.
d. Review the <Client> Minimum Acceptable Operational necessities list to confirm if enough resources square measure in situ to support operations
Coordinate commencement of knowledge system operations:
a. Recover important knowledge files and connected data once requested by EMT
b. Make sure that network and perimeter security is re-established at alternate location
c. Verify traditional, secure operation of systems and servers at alternate web site
d. Review the SanGrafix Minimum Acceptable Operational necessities list to confirm if enough resources square measure in situ to support operations
Business Continuity – Sprint Business. (2017). Sprint Business. Retrieved 14 March 2017, from https://business.sprint.com/solutions/business-continuity/?ECID=sem%3Aggl%3A20170303%3ADWASearch%3ANB%3AB2B%3APhrase%3ABusinessContinuity
Business Continuity Plan. Ready.Gov. Retrieved 14 March 2017, from https://www.ready.gov/sites/default/files/documents/files/BusinessContinuityPlan.pdf
Shinder, D. (2017). 10 Things You Should Cover In Your Business Continuity Plan. TechRepublic. Retrieved from http://www.techrepublic.com/blog/10-things/10-things-you-should-cover-in-your-business-continuity-plan/