![]() |
![]() |
||||
Library of Congress – Continuity of Operations Plan (COOP)SituationThe Library of Congress serves as the research arm of Congress, includes the U.S Copyright Office, and sustains and preserves a universal collection of knowledge and creativity for future generations. The Library of Congress employs extensive IT resources to digitize, search, and disseminate its holdings. IT is the enabling technology to make knowledge available to Congress, preserve and make available a comprehensive record of American history, and share its collections through the National Digital Library Program.
SPS - Problem Solved. SPS created a Continuity of Operations Plan (COOP) that specifies functions and procedures to continue or resume IT-supported operations following a disruption or emergency. The COOP defines roles, responsibilities, and lines of succession. It identifies possible disaster scenarios and corresponding corrective steps. SPS designed the plan to work in conjunction with other Library emergency and contingency plans, and emphasized formats that are easy to use, update, and distribute. SPS included call trees for assembling emergency teams and a decision tree leading to COOP-activations. For each activation phase and organizational unit, SPS defined checklists of steps required to implement the COOP and ensure continued system support. SPS assembled a drive-away kit for personnel deployed to the alternate facility, providing them basic tools, information, and materials required to establish connections, synchronize databases, and interact with system users. Methodology SPS employed a holistic approach, assigning domain experts to each COOP discipline and leveraging SPS infrastructure and software systems expertise. The project team consisted of business process experts, system and software architects, and network engineers. SPS conducted frequent team meetings to ensure discipline experts exchanged status information, avoided duplicate work, and synchronized their respective content.
Officials involved in continuity of operations planning often note that a "COOP not tested is no COOP at all." In full agreement with this observation, SPS conducted COOP testing, training, and exercise sessions using materials directly from the COOP. Based on these activities, SPS updated and clarified many areas of the COOP, ensuring that managerial and technical personnel could use the COOP during stressful rapid-reaction scenarios. In particular, the COOP clearly identified manual tasks and steps required to activate remote site COOP facilities. Lessons Learned SPS quickly realized that maintaining the COOP was as important as creating it. To ensure an always-ready COOP, SPS organized time sensitive data in discrete appendixes; each assigned to a responsible party, and included a section dedicated to COOP maintenance instructions. Additionally, SPS identified COOP tools to partially automate COOP update and publishing. Results The Library met its objective of complying with Circular 65 and has a usable and maintainable COOP. The single COOP document reduced the time and cost for COOP maintenance as compared to maintenance costs of other Library system documents and procedures. Client Benefits The LOC currently meets Federal Executive Branch Preparedness Circular 65 directives. The ITS is now able to respond to disasters by following a single set of procedures. About SPS Contact Information |
CASE FACTSSector: |
||||
| © 2005–2007 Software
Performance Systems, Inc. | Privacy Policy
7905 Malcolm Road · Suite 200 · Clinton, MD 20735 · 1.866.734.6777 · sps@goSPS.com |
|||||