Home > Articles > Information Technology

📄 Contents

  1. Management Reference Guide
  2. Table of Contents
  3. Introduction
  4. Strategic Management
  5. Establishing Goals, Objectives, and Strategies
  6. Aligning IT Goals with Corporate Business Goals
  7. Utilizing Effective Planning Techniques
  8. Developing Worthwhile Mission Statements
  9. Developing Worthwhile Vision Statements
  10. Instituting Practical Corporate Values
  11. Budgeting Considerations in an IT Environment
  12. Introduction to Conducting an Effective SWOT Analysis
  13. IT Governance and Disaster Recovery, Part One
  14. IT Governance and Disaster Recovery, Part Two
  15. Customer Management
  16. Identifying Key External Customers
  17. Identifying Key Internal Customers
  18. Negotiating with Customers and Suppliers—Part 1: An Introduction
  19. Negotiating With Customers and Suppliers—Part 2: Reaching Agreement
  20. Negotiating and Managing Realistic Customer Expectations
  21. Service Management
  22. Identifying Key Services for Business Users
  23. Service-Level Agreements That Really Work
  24. How IT Evolved into a Service Organization
  25. FAQs About Systems Management (SM)
  26. FAQs About Availability (AV)
  27. FAQs About Performance and Tuning (PT)
  28. FAQs About Service Desk (SD)
  29. FAQs About Change Management (CM)
  30. FAQs About Configuration Management (CF)
  31. FAQs About Capacity Planning (CP)
  32. FAQs About Network Management
  33. FAQs About Storage Management (SM)
  34. FAQs About Production Acceptance (PA)
  35. FAQs About Release Management (RM)
  36. FAQs About Disaster Recovery (DR)
  37. FAQs About Business Continuity (BC)
  38. FAQs About Security (SE)
  39. FAQs About Service Level Management (SL)
  40. FAQs About Financial Management (FN)
  41. FAQs About Problem Management (PM)
  42. FAQs About Facilities Management (FM)
  43. Process Management
  44. Developing Robust Processes
  45. Establishing Mutually Beneficial Process Metrics
  46. Change Management—Part 1
  47. Change Management—Part 2
  48. Change Management—Part 3
  49. Audit Reconnaissance: Releasing Resources Through the IT Audit
  50. Problem Management
  51. Problem Management–Part 2: Process Design
  52. Problem Management–Part 3: Process Implementation
  53. Business Continuity Emergency Communications Plan
  54. Capacity Planning – Part One: Why It is Seldom Done Well
  55. Capacity Planning – Part Two: Developing a Capacity Planning Process
  56. Capacity Planning — Part Three: Benefits and Helpful Tips
  57. Capacity Planning – Part Four: Hidden Upgrade Costs and
  58. Improving Business Process Management, Part 1
  59. Improving Business Process Management, Part 2
  60. 20 Major Elements of Facilities Management
  61. Major Physical Exposures Common to a Data Center
  62. Evaluating the Physical Environment
  63. Nightmare Incidents with Disaster Recovery Plans
  64. Developing a Robust Configuration Management Process
  65. Developing a Robust Configuration Management Process – Part Two
  66. Automating a Robust Infrastructure Process
  67. Improving High Availability — Part One: Definitions and Terms
  68. Improving High Availability — Part Two: Definitions and Terms
  69. Improving High Availability — Part Three: The Seven R's of High Availability
  70. Improving High Availability — Part Four: Assessing an Availability Process
  71. Methods for Brainstorming and Prioritizing Requirements
  72. Introduction to Disk Storage Management — Part One
  73. Storage Management—Part Two: Performance
  74. Storage Management—Part Three: Reliability
  75. Storage Management—Part Four: Recoverability
  76. Twelve Traits of World-Class Infrastructures — Part One
  77. Twelve Traits of World-Class Infrastructures — Part Two
  78. Meeting Today's Cooling Challenges of Data Centers
  79. Strategic Security, Part One: Assessment
  80. Strategic Security, Part Two: Development
  81. Strategic Security, Part Three: Implementation
  82. Strategic Security, Part Four: ITIL Implications
  83. Production Acceptance Part One – Definition and Benefits
  84. Production Acceptance Part Two – Initial Steps
  85. Production Acceptance Part Three – Middle Steps
  86. Production Acceptance Part Four – Ongoing Steps
  87. Case Study: Planning a Service Desk Part One – Objectives
  88. Case Study: Planning a Service Desk Part Two – SWOT
  89. Case Study: Implementing an ITIL Service Desk – Part One
  90. Case Study: Implementing a Service Desk Part Two – Tool Selection
  91. Ethics, Scandals and Legislation
  92. Outsourcing in Response to Legislation
  93. Supplier Management
  94. Identifying Key External Suppliers
  95. Identifying Key Internal Suppliers
  96. Integrating the Four Key Elements of Good Customer Service
  97. Enhancing the Customer/Supplier Matrix
  98. Voice Over IP, Part One — What VoIP Is, and Is Not
  99. Voice Over IP, Part Two — Benefits, Cost Savings and Features of VoIP
  100. Application Management
  101. Production Acceptance
  102. Distinguishing New Applications from New Versions of Existing Applications
  103. Assessing a Production Acceptance Process
  104. Effective Use of a Software Development Life Cycle
  105. The Role of Project Management in SDLC— Part 2
  106. Communication in Project Management – Part One: Barriers to Effective Communication
  107. Communication in Project Management – Part Two: Examples of Effective Communication
  108. Safeguarding Personal Information in the Workplace: A Case Study
  109. Combating the Year-end Budget Blitz—Part 1: Building a Manageable Schedule
  110. Combating the Year-end Budget Blitz—Part 2: Tracking and Reporting Availability
  111. References
  112. Developing an ITIL Feasibility Analysis
  113. Organization and Personnel Management
  114. Optimizing IT Organizational Structures
  115. Factors That Influence Restructuring Decisions
  116. Alternative Locations for the Help Desk
  117. Alternative Locations for Database Administration
  118. Alternative Locations for Network Operations
  119. Alternative Locations for Web Design
  120. Alternative Locations for Risk Management
  121. Alternative Locations for Systems Management
  122. Practical Tips To Retaining Key Personnel
  123. Benefits and Drawbacks of Using IT Consultants and Contractors
  124. Deciding Between the Use of Contractors versus Consultants
  125. Managing Employee Skill Sets and Skill Levels
  126. Assessing Skill Levels of Current Onboard Staff
  127. Recruiting Infrastructure Staff from the Outside
  128. Selecting the Most Qualified Candidate
  129. 7 Tips for Managing the Use of Mobile Devices
  130. Useful Websites for IT Managers
  131. References
  132. Automating Robust Processes
  133. Evaluating Process Documentation — Part One: Quality and Value
  134. Evaluating Process Documentation — Part Two: Benefits and Use of a Quality-Value Matrix
  135. When Should You Integrate or Segregate Service Desks?
  136. Five Instructive Ideas for Interviewing
  137. Eight Surefire Tips to Use When Being Interviewed
  138. 12 Helpful Hints To Make Meetings More Productive
  139. Eight Uncommon Tips To Improve Your Writing
  140. Ten Helpful Tips To Improve Fire Drills
  141. Sorting Out Today’s Various Training Options
  142. Business Ethics and Corporate Scandals – Part 1
  143. Business Ethics and Corporate Scandals – Part 2
  144. 12 Tips for More Effective Emails
  145. Management Communication: Back to the Basics, Part One
  146. Management Communication: Back to the Basics, Part Two
  147. Management Communication: Back to the Basics, Part Three
  148. Asset Management
  149. Managing Hardware Inventories
  150. Introduction to Hardware Inventories
  151. Processes To Manage Hardware Inventories
  152. Use of a Hardware Inventory Database
  153. References
  154. Managing Software Inventories
  155. Business Continuity Management
  156. Ten Lessons Learned from Real-Life Disasters
  157. Ten Lessons Learned From Real-Life Disasters, Part 2
  158. Differences Between Disaster Recovery and Business Continuity , Part 1
  159. Differences Between Disaster Recovery and Business Continuity , Part 2
  160. 15 Common Terms and Definitions of Business Continuity
  161. The Federal Government’s Role in Disaster Recovery
  162. The 12 Common Mistakes That Cause BIAs To Fail—Part 1
  163. The 12 Common Mistakes That Cause BIAs To Fail—Part 2
  164. The 12 Common Mistakes That Cause BIAs To Fail—Part 3
  165. The 12 Common Mistakes That Cause BIAs To Fail—Part 4
  166. Conducting an Effective Table Top Exercise (TTE) — Part 1
  167. Conducting an Effective Table Top Exercise (TTE) — Part 2
  168. Conducting an Effective Table Top Exercise (TTE) — Part 3
  169. Conducting an Effective Table Top Exercise (TTE) — Part 4
  170. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part One
  171. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Two
  172. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Three
  173. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Four
  174. The Information Technology Infrastructure Library (ITIL)
  175. The Origins of ITIL
  176. The Foundation of ITIL: Service Management
  177. Five Reasons for Revising ITIL
  178. The Relationship of Service Delivery and Service Support to All of ITIL
  179. Ten Common Myths About Implementing ITIL, Part One
  180. Ten Common Myths About Implementing ITIL, Part Two
  181. Characteristics of ITIL Version 3
  182. Ten Benefits of itSMF and its IIL Pocket Guide
  183. Translating the Goals of the ITIL Service Delivery Processes
  184. Translating the Goals of the ITIL Service Support Processes
  185. Elements of ITIL Least Understood, Part One: Service Delivery Processes
  186. Case Study: Recovery Reactions to a Renegade Rodent
  187. Elements of ITIL Least Understood, Part Two: Service Support
  188. Case Studies
  189. Case Study — Preparing for Hurricane Charley
  190. Case Study — The Linux Decision
  191. Case Study — Production Acceptance at an Aerospace Firm
  192. Case Study — Production Acceptance at a Defense Contractor
  193. Case Study — Evaluating Mainframe Processes
  194. Case Study — Evaluating Recovery Sites, Part One: Quantitative Comparisons/Natural Disasters
  195. Case Study — Evaluating Recovery Sites, Part Two: Quantitative Comparisons/Man-made Disasters
  196. Case Study — Evaluating Recovery Sites, Part Three: Qualitative Comparisons
  197. Case Study — Evaluating Recovery Sites, Part Four: Take-Aways
  198. Disaster Recovery Test Case Study Part One: Planning
  199. Disaster Recovery Test Case Study Part Two: Planning and Walk-Through
  200. Disaster Recovery Test Case Study Part Three: Execution
  201. Disaster Recovery Test Case Study Part Four: Follow-Up
  202. Assessing the Robustness of a Vendor’s Data Center, Part One: Qualitative Measures
  203. Assessing the Robustness of a Vendor’s Data Center, Part Two: Quantitative Measures
  204. Case Study: Lessons Learned from a World-Wide Disaster Recovery Exercise, Part One: What Did the Team Do Well
  205. (d) Case Study: Lessons Learned from a World-Wide Disaster Recovery Exercise, Part Two

During most of 2004 I worked as a business continuity consultant for a major financial services company headquartered in southern California with regional centers nation-wide. I was a member of a small team functioning as the company's business continuity department. One of our first recommendations was to solicit bids for a disaster recovery services contract. Our business justification clearly showed the need for a remote recovery site for both technical and business restorations in the event of a disaster. Executives promptly authorized us to proceed with the process.

We compiled a list of prioritized requirements and incorporated them into a comprehensive and formal request for proposal (RFP). Other necessary departments such as legal and purchasing helped to finalize the document and in early April the company's purchasing agent sent the RFP out to three prospective bidders: IBM, HP and Sungard. The prospective bidders had three weeks to send back their proposals, and with days to spare all three submitted competitive responses. We evaluated the proposals thoroughly, visited their recovery sites and talked with several of their customers. For a variety of reasons including cost, support, references, and capability of facilities, we awarded the contract to Sungard on June 1st.

Our team was eager to test and demonstrate Sungard's capabilities. During July and early August of that year I participated on a cross-functional team planning a simulated disaster recovery exercise. Our plan involved two aspects. One was to restore critical business functions at Sungard's business recovery center in Cypress, California which was some 30 miles from the company's headquarters. The other was to recover technical operations at Sungard's technical recovery center in Scottsdale, Arizona. All planning was proceeding smoothly. On August 12th, with just a week to go before the exercise, our planning efforts took a radical change.

Switching from Simulated Disaster to a Real Disaster

Tropical storm Charley in the Atlantic Ocean had grown into a full blown category 2 hurricane, and it was headed directly for Tampa, FL. My client has a large regional center in Tampa close to the gulf. On Thursday afternoon, August 12th, residents of the entire Tampa region were ordered to evacuate. For the next 72 hours our team suspended all planning for the simulated exercise, and went into full emergency mode to cope with a real-life disaster. We pulled together all necessary personnel, took preventative actions in Tampa to facilitate a recovery, and evaluated our options of re-locating the Tampa office functions to either New York or Chicago.

Even though New York was planning for the Republican convention, and hotel rooms and security were possible concerns, we quickly determined that New York would be the better of the two choices to facilitate a quick and successful recovery. IT, Facilities, Telecom, Administration, Security, Business Continuity and the Business Units all participated, locally and remotely, in the planning and decision-making process.

On Friday morning we met again to report status on various recovery plans that by now involved teams of personnel in southern California, in Tampa, and in New York. Managers also authorized flying in special support personnel to Orlando because they considered Tampa too dangerous a place to land at that time. After all of the technical teams gave their updates, the recovery team leader inquired if there were any other concerns to discuss. The business unit representative raised her hand and quietly asked what soon became a bombshell of a question, "What about the loan documents?"

All 13 of us in the meeting turned to her as the meeting leader responded, "What do you mean, the loan documents?" The business unit rep went on to explain how there were tens of thousands of loan documents in cardboard boxes on the first floor of the building. These documents were of loans that were in process, and by policy would be scanned in as electronic documents only after the loans had fully funded. Because the building was within a quarter mile of the gulf coast and forecasters predicted ten foot storm surges, the team's emphasis quickly switched from the recovery of very high tech systems to the safeguarding of very low tech, but critical, hardcopy records. For the next three hours staffers moved hundreds of cardboard boxes to higher levels and safer locations.

Mother Nature Takes a Turn for the Better

By Friday afternoon we had all of our plans in place and were about to activate them. Over 2 million people had evacuated the Tampa area and the hurricane had grown to a category 4 with winds up to 145 mph. Then, rather suddenly, hurricane Charley turned sharply to the right and made landfall just north of Fort Myers, about 100 miles south of Tampa. Within hours we were able to confirm that my client's Tampa office was relatively unaffected. All of this occurred on Friday the 13th.

We still had follow-up work to do the next day. Teams went in to assess the facility, restore power, and make other arrangements to ensure full operation by Monday morning. Aside from a few minor local phone company problems, there were no significant issues to report. The entire facility was back to full operation by Sunday morning. As we resumed our planning for the simulation exercise that would occur this week, it was hard to ignore the irony of what we had just experienced. We had talked about making our simulation as realistic as possible to be able to assess our emergency preparedness. Formulating contingency plans for a real-life category 4 hurricane directly in your path is about as realistic as one can get. Much was learned from the experience. And fortunately for all involved, the quick and thorough contingency plans never had to be activated.

Lessons Learned

The recovery team learned several important lessons from this preparation. One was the importance of having emergency supplies on hand such as flashlights, batteries and water. The second was the need to have petty cash available. Lengthy, widespread power outages knocked ATMs out of service for up to ten hours in some areas. Most persons relied solely on ATMs or credit cards for purchases and during power outages cash was the only way to buy needed items.

The most important lesson was not to overlook the importance of critical documents. After days of planning, evaluating and addressing every possible technical contingency, the recovery learned that vital hardcopy records turned out to be one of the most crucial of elements. For all of our emphasis on advanced technology, there is still a large portion of corporations that rely on non-technical hardcopy materials and these need to be included in any recovery plan. This was the most significant lesson of all.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.