My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Res 2013-090/Approving a service agreement between Cash Cycle Solutions, Inc. for the Utility Billing and Notice Services
San-Marcos
>
City Clerk
>
03 Resolutions
>
2010's
>
2013
>
Res 2013-090/Approving a service agreement between Cash Cycle Solutions, Inc. for the Utility Billing and Notice Services
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/20/2014 9:59:52 AM
Creation date
6/27/2013 10:34:55 AM
Metadata
Fields
Template:
City Clerk
City Clerk - Document
Resolutions
City Clerk - Type
Approving
Number
2013-90
Date
6/18/2013
Volume Book
198
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
68
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
Cash Cycle Solutions, Inc. <br />Business Recovery Plan <br />Work Group: Accounting Location: San Diego, CA <br />Notification Level: 1 <br />Work Group: Operations Location: San Diego, CA <br />Notification Level: 1 <br />Office Phone <br />Cell Phone <br />Home Phone <br />Loan Nguyen <br />858 - 560 -2055 ext 105 <br />619- 2182792 <br />619- 449 -7913 <br />Work Group: Operations Location: San Diego, CA <br />Notification Level: 1 <br />3.2. Develop Consolidated Action Plan <br />The resulting Consolidated Action Plan (section 9.2 and following) summarizes the specific <br />strategies and actions selected to address the particular incident. The choice of these <br />strategies may depend upon the amount of damage sustained as a result of the incident and the <br />surviving operational capability. <br />3.2.1 Participate in Preliminary Incident Assessment <br />The INCIDENT MANAGEMENT TEAM will conduct a preliminary evaluation of the situation to <br />determine what operations are affected and which strategies and plans will be activated. <br />Document the incident circumstances, using the INCIDENT OBJECTIVES AND <br />STRATEGIES FORM (section 9.2.1) found in the Attachments Section below. <br />2. Document each significant finding and /or milestone, using the INCIDENT <br />STATUS SUMMARY FORM (section 9.2.4) found in the Attachments Section <br />below. Depending upon the incident circumstances, this form may be maintained <br />on a white board for easy reference and visibility. <br />3. Review available information regarding the incident such as areas affected, <br />status of communications, etc. <br />4. Determine and document the probable length of outage, considering such issues <br />as: <br />Severity of damage, if any; <br />Similar past experiences (e.g. power outages); <br />12 <br />Office Phone <br />Cell Phone <br />Home Phone <br />Mike Thornburg, <br />Director of Operations <br />858 - 560 -2055 ext 114 <br />619- 884 -2715 <br />619- 449 -7913 <br />3.2. Develop Consolidated Action Plan <br />The resulting Consolidated Action Plan (section 9.2 and following) summarizes the specific <br />strategies and actions selected to address the particular incident. The choice of these <br />strategies may depend upon the amount of damage sustained as a result of the incident and the <br />surviving operational capability. <br />3.2.1 Participate in Preliminary Incident Assessment <br />The INCIDENT MANAGEMENT TEAM will conduct a preliminary evaluation of the situation to <br />determine what operations are affected and which strategies and plans will be activated. <br />Document the incident circumstances, using the INCIDENT OBJECTIVES AND <br />STRATEGIES FORM (section 9.2.1) found in the Attachments Section below. <br />2. Document each significant finding and /or milestone, using the INCIDENT <br />STATUS SUMMARY FORM (section 9.2.4) found in the Attachments Section <br />below. Depending upon the incident circumstances, this form may be maintained <br />on a white board for easy reference and visibility. <br />3. Review available information regarding the incident such as areas affected, <br />status of communications, etc. <br />4. Determine and document the probable length of outage, considering such issues <br />as: <br />Severity of damage, if any; <br />Similar past experiences (e.g. power outages); <br />12 <br />
The URL can be used to link to this page
Your browser does not support the video tag.