Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 163
CHAPTER FIVE Long-Term Reliability and Sustainability of Warning Center Operations SUMMARY This chapter evaluates long-term prospects of the two Tsunami Warning Centers (TWCs) to providing reliable and internally consistent tsunami detection, decision support, and product generation, and for effectively supporting threat detection, warning management, and public response. The goal of the current geographically distributed organization of the TWCs (i.e., a center each in Hawaii and Alaska) with distinct areas of responsibility (AORs) is to provide the system with back-up in the case of critical failure at the other center. However, the two TWC technology suites differ considerably from each other, and those differences lead to techno- logical incompatibilities and limited capabilities for back-up, redundancy, and checks and bal- ances, which are important mission capabilities for the tsunami warning system. In addition, as discussed in detail in Chapter 3, inconsistencies in warning products issued by the two TWCs and the current division of AOR results in messages that have caused confu- sion and the potential to cause confusion in the future, making the products less effective in eliciting the appropriate response. The committee recommends that the National Oceanic and Atmospheric Administration’s (NOAA’s) National Weather Service (NWS) develop tsunami warning system products that reflect best practices, as well as lessons learned from other operational real-time, large-scale, mission-critical distributed systems, and that comply with international information technology and software engineering product and process stan- dards. In addition, the committee recommends that the TWCs undertake an external review by information technology (IT) specialists in the area of communication technology for the latest technology in message composition software and formats to ensure compatibility with current and next generation information and communication technology (web and cell-phone) for message dissemination. Because the centers are under different management, use different analytical software and hardware, and appear to have distinct organizational cultures, the committee concludes that they do not function as redundant systems. The committee discuses several options for alternative organizational structures including operational convergence of the two centers, merging the two centers into a single center, and/or co-locating center(s) with other research or operational units and recommends that the decision to develop an organizational structure 

OCR for page 163
T S U N A M I WA R N I N G S A N D P R E PA R E D N E S S for the TWCs should be undertaken as part of the comprehensive, enterprise-wide, long-range planning effort recommended in this chapter. The success of the TWC mission is critically dependent on technical infrastructure and human capital, both of which the committee assessed to be insufficiently supported. Because of the rapid evolution of IT and its importance in the overall process of detecting and warning, the committee found that the TWCs lack sufficient state-of-the-art technology; IT support, maintenance, assessment and planning processes; and IT personnel and leadership. The com- mittee recommends that NOAA/NWS provide these capabilities to the TWCs and establish an external IT advisory body, with membership from the U.S. Geological Survey (USGS), other seismic network operators, social and information scientists, emergency managers, and other large-scale, safety-critical systems professionals to advise the TWCs. Workforce development and recruitment can be challenging. Frequent, regular, and varied types of training as well as stronger connections with the external research community are required. TWC human capital requirements, training, re-training, development, and mentoring and requirements for professional exchanges should be included, reassessed, and updated as part of the recommended enterprise-wide tsunami planning effort, so that technology and human and organizational requirements can be considered and developed together by tsunami program members and their customers. Overall, the TWCs should adopt NOAA- and government-wide standards for recruiting, retaining, training and re-training, planning, devel- oping, nurturing, and mentoring the critical human resources that are at the center of tsunami warning and detection system success. Finally, the committee found that an organizational culture change within the NOAA/NWS Tsunami Program would be beneficial to advance operational excellence. Such a change should also lead to increased support to adopt national and international standards, processes, best practices and lessons learned for all functions, technologies, and processes and products; and result in ongoing, continuous process improvements. As detailed in the chapter, some of the steps to improve long-term operations recom- mended by the committee include the following: • NOAA/NWS should undertake a comprehensive, enterprise-wide, long-range planning effort for the TWCs. The goal of the planning effort would be to analyze TWC func- tions and requirements; articulate the technological, human, physical, and intellectual infrastructure required to meet the TWC requirements; and integrate the technology, applications, tools, processes, networks, leadership, policies, organizational structures, and human capital required to provide long-term reliable and sustainable global TWC operations. Such a technology planning effort should develop assessments of: o technology, applications, tools, processes, networks, hardware, software, and systems; o the requirements for human capital, training, re-training, development, mentoring, professional exchange, leadership, and policies; and o the organizational structure(s) required to ensure that the two TWCs can function 

OCR for page 163
Long-Term Reliability and Sustainability of Warning Center Operations as a single warning center and can provide the required support for reliable and sustainable global TWC operations. • NOAA/NWS and the TWCs should adopt national, and where available, international, standards, best practices, and lessons learned for all functions, technology, processes, and products. • If NOAA/NWS maintains the current organizational structure, then it should harmonize and standardize technologies, processes, and products between the two TWCs. • NOAA/NWS and the TWCs should undertake ongoing, joint, or NOAA-wide bench- marking and continuous process improvement activities for their functional, techno- logical, organizational, or human capital initiatives; report those activities internally and externally; and incentivize excellent performance as well as best practices. • NOAA/NWS and the TWCs should develop measures of performance and benchmark individual, organizational, and technical performance against industry and agency metrics; identify areas for improvement; set short- and long-term performance goals; develop reward and incentive systems for such goals; and celebrate TWC and agency accomplishments as performance improves, in order to raise the level of TWC perfor- mance to that expected of a high-reliability organization. • NOAA/NWS and the TWCs should increase their use of internal and external review processes, as detailed below. THE TSUNAMI WARNING CENTERS The Pacific Tsunami Warning Center (PTWC) was established as the Honolulu Observatory in 1949 after the April 1, 1946, tsunami generated in the Aleutian Islands1 caused casualties and damage on the Hawaiian Islands. Following the 1960 Chile tsunami, the Honolulu Observatory expanded its AOR to cover all nations along the Pacific basin (Intergovernmental Oceano- graphic Commission, 1965). After the 2004 Indian Ocean tsunami, the PTWC’s responsibility was again expanded to include the Indian Ocean and Caribbean Sea nations. The West Coast/Alaska Tsunami Warning Center (WC/ATWC) was established as the Palmer Observatory after the great 1964 Alaskan earthquake, which devastated parts of Anchorage. In the 1980s and 1990s, its AOR was expanded to include tsunami warnings for California, Oregon, Washington, and British Columbia if potential tsunamigenic earthquakes were detected in their coastal areas. This delineation was changed in 1996 to include all Pacific-basin tsunami- genic sources for California, Oregon, Washington, British Columbia, and Alaska. After the 2004 Indian Ocean tsunami, the WC/ATWC’s responsibility expanded to include the U.S. Atlantic and Gulf coasts, Puerto Rico, the Virgin Islands, and the Atlantic coast of Canada. The PTWC has the following areas of responsibility (Figure 5.1): • the State of Hawaii • Guam, American Samoa, and other U.S. Pacific assets 1 Weinstein, 2008. 

OCR for page 163
T S U N A M I WA R N I N G S A N D P R E PA R E D N E S S FIGURE 5.1 Areas of responsibility (AORs) for the PTWC (dark gray) and the WC/ATWC (light gray). SOURCE: Government Accountability Office, 2010. Figure 5.1.eps bitmap • many Pacific rim countries (as an operational center of the Pacific Tsunami Warning and Mitigation System [PTWS] of the Intergovernmental Oceanographic Commission [IOC] occasioned by the 1960 Pacific-wide tsunami generated in Chile) • Indian Ocean countries (as an interim center for the Indian Ocean Tsunami Warning and Mitigation System [IOTWS] of the IOC since 2005) • Caribbean countries except the U.S. commonwealth of Puerto Rico and the U.S. and British Virgin Islands (as interim center for the Intergovernmental Coordination Group for the Tsunami and Other Coastal Hazards Warning System for the Caribbean and Adjacent Regions [ICG/CARIBE EWS] since 2006) The WC/ATWC has the following areas of responsibility (Figure 5.1): • all U.S. states except Hawaii • Canadian coastal regions • Puerto Rico and the Virgin Islands 

OCR for page 163
Long-Term Reliability and Sustainability of Warning Center Operations TSUNAMI WARNING CENTER FUNCTIONS The Tsunami Warning Centers have a widespread client base: emergency managers, the scientific community, and the public. They are responsible for gathering information from sensor and observational systems; detecting events of interest (tsunamigenic earthquakes) and determining magnitudes for those events; developing decision support information for operational and scientific decision makers; and providing and disseminating warning and noti- fication products to the public and other entities. The TWCs are not designed for or capable of detecting landslide-induced tsunamis such as those that might occur in Alaska, Puget Sound, or in some of the Hawaiian Islands. Operational components of each TWC (Figure 5.2) include: • Earth Data Observations, which allow the detection of earthquakes and tsunami occur- rence (described in Chapter 4). • Data and Information Collection of seismic and sea-level data, impact reports from agencies and the public, and data and information sharing with other centers (described in Chapter 4). FIGURE 5.2 Key operational components of the tsunami warning centers. SOURCE: U.S. Indian Ocean Tsunami Warning System Program, 2007. New 5.2 broadside 

OCR for page 163
T S U N A M I WA R N I N G S A N D P R E PA R E D N E S S • Tsunami Detection Systems that rely upon scientific expertise and practical experience to process and analyze the gathered data in support of tsunami detection and impact projections, and hardware and software that support the analysis. Critical to effective detection system performance are appropriate personnel, training, policies, proce- dures, and an organizational culture that values constant and frequent organizational learning and that reinforces the core goals of excellence and high performance in the warning system. • Tsunami Warning Center Decision Support Systems that assist the TWC watchstander2 in determining what type of warning product should be issued. Tools available to support the decision making process include criteria and bulletin thresholds, software support to detect seismic events in real time, and computer models of tsunami wave heights and coastal inundation models for impact assessments. Critical needs for this component include frequent and varied training for operational watchstanders (e.g., simulations, walk throughs, case studies, table-top exercises); organizationally sup- ported interactions between watchstanders in the two warning centers; and ongoing and prioritized research and development to support operations and implement new technology. • Warning and Other Products, which are standardized messages issued to the public and other customers. The following four products are described in detail in this chapter: o A Tsunami Warning, issued when a potential tsunami with significant widespread inundation is imminent or expected. Initial warnings are normally based only on seismic information. o A Tsunami Watch, issued to alert emergency managers and the public of an event that could later impact the watch area. As updated information becomes available (e.g., from sea level networks), the watch may be changed to a warning or advisory. o A Tsunami Advisory, issued for the threat of a potential tsunami causing strong currents or waves that would be dangerous to those in or near the water. Signifi- cant widespread inundation is not expected for those areas under an advisory. o A Tsunami Information Statement, issued to alert emergency managers and the public that an earthquake has occurred. In most cases, information statements are issued to indicate that there is not a threat of a destructive tsunami affecting the T WC’s AOR, and are used to avoid evacuations in coastal areas that may have felt the earthquake. In some cases, the information statement is also used to indicate the need to stay tuned for more information as it becomes available. o Dissemination and Notification Plans, which are produced in advance to ensure that TWC customers are able to receive and understand the warning products. It is critical that dissemination systems are tested and that roles and responsibilities for different actors are clearly defined and articulated. 2 A watchstander is a person who stands a shift (a watch) in an operational command center, such as those centers that monitor earthquakes, storms, emergency events, electrical and power failures, and the operation of various plants, factories, emergency services operations, equipment, and vessels. 

OCR for page 163
Long-Term Reliability and Sustainability of Warning Center Operations • Community Connections that educate the public about tsunami safety and prepared- ness and inform the public about the TWC’s role in tsunami warning. Effective commu- nity connections include partnerships with media and the community that develop community preparedness and other resilience initiatives (U.S. Indian Ocean Tsunami Warning System Program, 2007) (community preparedness efforts are discussed in detail in Chapter 3). Tsunami Detection Tsunami detection requires information gathering, data analysis and assessment, and decision making and communication. Earthquake detection functions required at both the TWCs are similar and comprise the following basic steps (see Weinstein, 2008; Whitmore et al., 2008): (1) Seismic data analysis systems automatically and rapidly evaluate the location, size, and focal mechanism of an earthquake to determine if it has significant potential to trigger a tsunami. Watchstanders reassess the event by analyzing select seismic data and may empirically adjust the moment magnitude determination; (2) Watchstanders determine if the magnitude is above certain thresholds and based on this analysis, generate and disseminate initial messages (with either a watch, warning, or information bulletin); (3) For each significant earthquake, watchstanders estimate corresponding tsunami arrival times and heights for selected critical locations; (4) Once sea level data are acquired, watchstanders reassess the threat, including scaling earlier, computed tsunami forecast scenarios to fit the sea level observations from the Deep-ocean Assessment and Reporting of Tsunamis (DART) systems; if needed (e.g., if sea level data are lacking) watchstanders continue post-processing the seismic data to refine the threat assessment; (5) Watchstanders generate and disseminate follow-up informational messages with the additional detailed information available from sea level and seismic data analysis (National Oceanic and Atmospheric Administration, 2008a, c); (6) Watchstanders iterate steps 5 and 6 until an appropriate time interval (based on the expected tsunami propagation speed and modeled duration of inundation) has passed and all watches or warnings for the AOR shorelines can be lifted. The TWCs consider “significant” earthquakes as events exceeding certain predetermined magnitude thresholds, which also depend on the distance offshore. These events automatically trigger the audio alarm systems of the two TWCs, prompting on-duty watchstanders to initi- ate a detailed investigation of the earthquake and its potential to trigger tsunamis. Typically, watchstanders at both TWCs are required to make initial and independent estimates of the earthquake location and magnitudes within 5 to 15 minutes of the earthquake origin time (Na- tional Oceanic and Atmospheric Administration, 2008a, c). The location determines which TWC 

OCR for page 163
T S U N A M I WA R N I N G S A N D P R E PA R E D N E S S will be responsible for officially determining earthquake parameters. Based on the committee’s review of the warning messages, magnitude determinations included in the warning mes- sages sometimes differ between the two TWCs. The warning message is communicated to the National Earthquake Information Center (NEIC, see also Box 5.1) but the TWCs typically attempt to determine the seismic location and magnitude more rapidly than NEIC. Subsequent mes- sages from the TWCs may include corrections to the magnitude determination issued in the first message. Given the benefit of consistency in warning message dissemination (discussed in Chapter 3), avoiding such inconsistencies in earthquake parameters between different warning products would be beneficial to the warning process. Although many of the required functions are similar, the detection procedures followed by each of the TWCs differ and the centers use different operating systems and graphical user inter- faces (Table 5.1). The WC/ATWC uses personal computer (PC) workstations running Microsoft Windows and all seismic, sea level, geographic information system (GIS), forecasting, and product-generation software run on a network of 10 operational PCs with complete hardware and communications redundancy. Development, testing, and training operations are performed on three other computers. In contrast, the PTWC utilizes seven redundant Sun/Solaris work- stations, and functions are migrating to the open-source Linux operating system. The develop- ment of incompatible hardware platforms was based on the availability of local knowledge at each TWC, rather than on a formal information architecture development or planning process. Each TWC uses different software for its real-time monitoring and analysis systems: the PTWC runs Antelope3 to manage seismic data streams. This software package is currently used at several other earth science programs (e.g., Earthscope Array National Facility, Saudi Arabia National Seismic Network, Alaska Seismic Network, Singapore National Telemetry Network, Dominican Republic Seismic Network, Ocean Observatories Initiative Cyberinfrastructure com- ponent). The WC/ATWC and the PTWC use software based on Earthworm (version 7.1), an open source package for regional seismic networks developed by the USGS in 1993. As of 2007, 40 observatories4 in addition to the WC/ATWC and the PTWC were using Earthworm despite the lack of active software development or maintenance. Because there is no common software architecture, each TWC operates with a different set of standards and procedures. The processes followed by scientists receiving sensor information differ and are supported by different analytical tools in each TWC. The analyses, results, mes- sages, thresholds, and notification processes supported by each TWC’s hardware and software technology are also therefore different, and the customer-facing software interfaces and re- ports provided to the public and the media from each TWC differ; the result of the differences suggests that the two TWCs are not part of the same organization, with the same mission. The differences introduce another set of operational challenges, as, based on the committee’s observations, it appears that a scientist working at one TWC would have difficulty covering a shift at the other TWC without significant additional training. Despite these differences, how- 3 http://www.brtt.com/. 4 The list was obtained from http://folkworm.ceri.memphis.edu/ew-doc/. 0

OCR for page 163
Long-Term Reliability and Sustainability of Warning Center Operations BOX 5.1 Other Operational Organizations As part of the National Weather Service, the National Centers for Environmental Predictions (NCEP) provides overarching management for several operational prediction and modeling centers (e.g., Aviation Weather Center [AWC], Storm Prediction Center [SPC], or National Hurricane Center [NHC]).These centers provide a range of operational products, such as accurate analyses, guidance, forecasts, and warnings in support of NOAA’s mission to protect life and property. The centers are all managed under NCEP to increase the exchange of lessons learned among operational units and to provide central leadership to capitalize on emerging scientific and technological advances (NOAA/NCEP strategic plan 2009-2013). The NEIC is part of the USGS and its mission is to determine promptly the location and size of destructive earthquakes worldwide. The center disseminates the results of its analysis immediately to the public and to the user-community, including emergency response agencies. TABLE 5.1 Comparison of Tsunami Warning Center Technology and Management Products and Processes Technology Product, West Coast/Alaska Pacific Process Tsunami Warning Center Tsunami Warning Center Hardware Platforms Hardware Platforms 10 PC workstations and 7 Sun workstations servers with hardware and 2 PC workstations from PMEL to run communications redundancy SIFT Software Platforms Operating System Windows XP for EarlyBird SUN Solaris and Linux Applications • Seismic processing, Data acquisition: Earthworm and Data acquisition: Earthworm, Nanometrics for WC/ATWC network EdgeCWB, and Antelope for PTWC analysis data network data Data processing: standard Data processing: for non-Hawaii Earthworm architecture with events, standard Earthworm specialized tsunami analysis architecture with local developed modules known as EarlyBird user interfaces and some use of EarlyBird modules. For Hawaii events, locally developed analysis system • Sea level, tidal data Data ingest through Global Telecommunications System (GTS) and Earthworm using locally developed decode software analysis Data analysis using TideView Data analysis using TideTool continued 

OCR for page 163
T S U N A M I WA R N I N G S A N D P R E PA R E D N E S S TABLE 5.1 Continued Technology Product, West Coast/Alaska Pacific Process Tsunami Warning Center Tsunami Warning Center • Mapping software EarthVu GIS—locally developed GMT open source software based on Geodyssey Limited’s maintained at the University of Hawaii Hipparchus system. Also use Generic Mapping Tool (GMT) and developing with ESRI and Google Maps • Messaging software Written internally Aging—software support difficult Watchstander previews are not supported Coded in C Coded in FORTRAN • Geographic EarthVu information system • Tsunami forecasting Use Alaska Tsunami Forecast Model (ATFM) through EarthVu GIS interface Use PMEL’s SIFT server software and hardware systems Precomputed model database Developing forecast system capable WC/ATWC developing ATFM of producing international forecasts version 2, an upgrade to ATFM known as real-time inundation forecasting of tsunamis Will use ATFM version 2 once available • Product formats Standard NWS, HTML, RSS, CAP/ Standard NWS, RSS, CAP/XML, SMS XML, SMS • Configuration Subversion Configuration GIT Management System management tools Configuration Management Plan (CMP) in use • Security, quality Recently completed a Certificate Ready to undergo Certificate and and Accreditation audit (May 2010). Accreditation audit assurance, file sharing Authority to operate granted with software moderate threat level. Programming C Procedural—C, FORTRAN Languages Some Java-based code Tcl/TK for scripting Databases MySQL Web Infrastructure HTML, PHP, MapTools PHP Web 2.0, 3.0 Planning, Not described Initial explorations Products continued 

OCR for page 163
Long-Term Reliability and Sustainability of Warning Center Operations TABLE 5.1 Continued Technology Product, West Coast/Alaska Pacific Process Tsunami Warning Center Tsunami Warning Center Technology Life Cycle Processes System Planning Not observed Processes System Development Software is internally developed, during periods of operational slack, by Processes watchstanding scientists. IT support staff express reservations about stability of hardware, software infrastructure. System Deployment Performed by watchstanding scientists, during periods of operational Processes slack Release deployment follows CMP’s instructions and requirements System Testing Development and test systems Not described Processes provide testbed before systems are operationally deployed. CMP provides testing requirements. System Support Watchstanding scientists maintain the pieces of code that they are responsible for developing. IT support staff report software is unstable and aging. System Procurement Informal Processes Dated Inadequately budgeted System Maintenance Regularly performed Informal processes System Configuration No formal processes described No formal processes described Management Updates difficult IT support staff performing updates and installing changes impacted by unstable and aging software. Organizational Not observed Learning Processes, Process Improvements, Incorporation of Lessons Learned, Dissemination of Best Practices continued 

OCR for page 163
T S U N A M I WA R N I N G S A N D P R E PA R E D N E S S wide technology architecture for TWC operations and the accompanying enterprise-wide technology support processes. Recommendation: Given the importance of technology, particularly IT, in the overall process of detecting and warning, and the rapid evolution of IT, NOAA/NWS should provide the TWCs with stronger IT commitment and leadership, and greater resources for software and hardware personnel, planning, development, operations, maintenance, and continuous process and product improvement. Recommendation: IT staff should be provided to the TWCs so that IT hardware and software design, development, and maintenance are not a collateral duty of a watchstanding scientist, as is the case presently. An external IT Advisory Board, with membership from the USGS, other seismic network operators, human factors, information technology, and other large-scale, safety-critical systems professionals should be established to advise the TWCs. The Board should meet on at least an annual basis and provide TWC management and operational personnel with guidance and expertise in building, developing, maintaining, and nurturing a highly effective, large-scale distributed, tsunami warning system. Six elements are critical to the enterprise-wide planning effort: highly effective leadership; a common set of functional, operational, and organizational processes; adherence to interna- tional standards; assessment processes that lead to continuous improvement; effective and compelling communication; and adequate and consistent funding to ensure that the pro- cesses, people, organizational structures, and policies effectively support the tsunami mission. Specifically, the committee recommends the following improvements: Senior IT leadership to guide the organization and ensure that the TWC technology archi- tecture supports TWC operational requirements for reliability and sustainability; • A common set of functional, operational and organizational processes, including o Articulated technology development, procurement, deployment, maintenance, sup- port, security, and configuration management processes; o Planning processes that are compliant with software engineering and computer science standard processes and lessons learned from other large-scale, mission- critical systems, and which are effectively carried out by TWC IT management and staff personnel, IT support personnel, in regular consultation with TWC customers and emergency management personnel; o An enterprise-wide IT requirements development process that transparently identi- fies all TWC requirements with a single planning process and a single enterprise- wide IT architecture; and o IT development, deployment, maintenance, support, quality assurance, security, and configuration management processes that are adequately planned and budgeted, 

OCR for page 163
Long-Term Reliability and Sustainability of Warning Center Operations and undertaken by IT and software engineering professionals following current IT development and deployment practices; • Adherence to international standards, including adoption of current international software engineering, process, documentation, hardware, and software standards throughout the tsunami system; • Assessment processes that lead to continuous improvement, including o Yearly systemwide performance monitoring, management, testing and bench- marking; yearly assessment, evaluation, accountability audits, and reporting of the T WC technology infrastructure’s support for the long-term reliability and sustain- ability of TWC operations; o Common, systemwide performance metrics and benchmarks; and o Incentives to ensure compliance with standards and high levels of performance; • Mechanisms to communicate best practices, lessons learned and to enhance organiza- tional learning; and • Adequate, substantial, multi-year, dedicated funding for all elements of the technology plan. Multi-year funding to support the technology planning, development, deployment, main- tenance, support, and security operations will need to be appropriately budgeted over the technology life cycle. As part of this planning and modernization process the committee identifies an additional urgent need: • Attention should be paid to the use of traditional, nontraditional, and next generation technology in support of community outreach and dissemination. IT for community outreach and dissemination efforts should be included as part of the long-range technology planning process and should be incorporated as an ongoing component of TWC planning processes. Recommendation: NOAA/NWS and the TWCs should adopt national, and where applicable, international, standards, best practices, and lessons learned for all functions, technology, processes, and products. Specifically, the TWCs should develop platform- independent hardware and software architectures, applications, and interfaces; and employ international hardware and software planning, development, operations, and maintenance product and process standards, including the Software Engineering Institute’s Capability Maturity Model and the software development life cycle (Carnegie Mellon Software Engineering Institute, 2010). Recommendation: The TWCs should also regularly and systematically apply continuing process and product improvement models for hardware and software planning, development, operations, and maintenance; organizational processes; and should develop a learning organizational culture. 

OCR for page 163
T S U N A M I WA R N I N G S A N D P R E PA R E D N E S S HUMAN RESOURCES Each TWC is staffed by a center director, a tsunami warning science officer (who serves as the deputy director), an information technology officer, nine science duty staff (geophysicists and physical oceanographers), a senior electronics technician, an electronics technician, and an administrative assistant (Charles McCreery, presentation to the committee, 2008). The nine science duty staff members perform watchstanding duties in addition to their research and development duties (National Oceanic and Atmospheric Administration, 2008b, c). Because of the watchstander’s critical role in maintaining situational awareness and issuing correct notifi- cation and warning products, the committee reviewed this position’s shift schedules, training, support, and responsibilities as part of its assessment of the TWC’ long-term sustainability. When the TWCs are fully staffed, the nine watchstanders serve on rotating two-person, eight-hour shifts that provide 24/7 coverage. Both TWCs have identical watch schedules (0800-1600, 1600-2400, 2400-0800 local time), although the two watch centers are in different time zones. Watches can be rotated to cover busy periods, vacations, and other TWC needs. Two watchstanders are always present at the WC/ATWC. In contrast, the PTWC has only one on-duty watchstander in the watch station at all times, while the second watchstander is on a 90-second response standby, allowing him/her to sleep or to be outside the watch station. Each watchstander is responsible for checking all workstations every four hours to ensure functionality. Unless they need to respond to an event, watchstanders spend approximately six hours on software development and two for operational activities (Paul Whitmore, West Coast and Alaska Tsunami Warning Center, personal communication). When an alarm is sounded, the watchstanders leave their other duties to respond. Because they are most often attending to other duties, there is an indeterminate period of time required for watchstanders to acclimate themselves to an alarm. The WC/ATWC rotates watches every two weeks, which can result in sleep disorders (Sack et al., 2007) and work/life balance issues, but provides equitable sharing of night shift watch- standing duties. Resulting sleep disorders, issues with work/life balance, as well as several month-long shortages of two full-time watchstanders at the WC/ATWC in 2008 suggest that staff fatigue may be an issue. T WC staff have varying levels of engagement with the external research community. The PTWC’s proximity to Honolulu (23 miles away) is conducive to interactions with the civil defense and academic communities at the University of Hawaii at Manoa, while WC/ATWC’s distance from Anchorage (43 miles away) and its location in a small town of 7,000 residents (Palmer, Alaska) does not lend itself as easily to such interactions. Conclusion: Because of the importance of technical and scientific know-how within the T WC program, opportunities for interactions between TWC staff and the external scientific and professional communities are important, need to be encouraged and institutionalized within the tsunami program, and require adequate resources. Such interactions might include attendance at professional conferences; participation in seminars, workshops, or other structured learning opportunities; scientific and personnel 

OCR for page 163
Long-Term Reliability and Sustainability of Warning Center Operations exchanges and sabbaticals; study away opportunities at related scientific venues; and grants, fellowships, and stipends to further professional study. The watchstander has a critical role in tsunami decision support by maintaining situational awareness and issuing the correct products and information. Although visualization software assists by monitoring seismic and sea level data and mapping event locations, it is the watch- standers’ training, experience, and scientific expert judgment that are essential in making the appropriate decisions when creating notification products for emergency managers, local government, and the general public. Tsunami detection and warning requires frequent, effective, and purposeful communica- tion and interactions between watchstanders, staff, and management in the TWCs, and with operational decision makers and the public. To enhance the effectiveness of TWC decision making and the TWC staff’s ability to inform decision making processes of their customers, frequent, regular, and varied types of training for operational watchstanders (e.g., simulations, walk throughs, case studies, table-top exercises) are needed. In addition, scheduled and orga- nizationally supported interactions between watchstanders and management in distributed watch centers are beneficial to the TWCs’ reliability of operations; these activities could include seminars, personnel and information exchanges, technical meetings, and scheduled joint work sessions. Conclusion: Given the highly technical and specialized skill sets required for tsunami watchstanding, workforce development and recruiting can be challenging. The success of the TWC mission is critically dependent on human resources for tsunami warning and detection. Conclusion: Given the importance of technology in the overall process of tsunami detection and warning, and the rapid evolution of IT, stronger IT commitment and leadership and greater human resources devoted to IT are required in the TWCs. The TWCs lack senior IT leadership to support TWC operations, guide the enterprise-wide technology planning efforts, and provide guidance in adopting enterprise-wide technology processes. Conclusion: The TWCs require frequent, regular, and varied types of training for operational watchstanders (e.g., simulations, walk throughs, case studies, table-top exercises); frequent, regular, and organizationally supported interactions between watchstanders in distributed watch centers; and ongoing, funded, and prioritized research and development to support operations, which requires an explicit process for implementing new technology into operations. Recommendation: Because of the importance of technical and scientific expertise to the TWCs’ functions, TWC human capital requirements and TWC recruiting, training, re- training, development, mentoring, and professional exchange needs should be included, re-assessed, and updated as part of the NOAA/NWS enterprise-wide technology planning effort, and should be consistent with NOAA- and government-wide standards, so that 

OCR for page 163
T S U N A M I WA R N I N G S A N D P R E PA R E D N E S S technological, human, and organizational requirements can be considered and developed together by Tsunami Program members and their customers. As part of the process of maintaining and developing expertise in the TWCs, opportunities for interactions between TWC staff and external scientific and professional communities could be funded, encouraged, and institutionalized within the Tsunami Program. Such interactions might include drafting and implementing a formal plan for maintaining and increasing scien- tific currency; attendance at professional conferences; participation in seminars, workshops, or other structured learning opportunities; scientific and personnel exchanges and sabbaticals; study away opportunities at related scientific venues; and grants, fellowships, and stipends to further professional study. ORGANIZATIONAL STRUCTURES Tsunami detection and warning is currently undertaken by multiple, distributed members linked together to achieve a goal: management of and response to a tsunami disaster. As indicated in the first chapter, the tsunami warning system needs to exhibit properties of a high-reliability organization (HRO), sharing common processes that are supported by distrib- uted information technology (Davidow and Malone, 1992; Mowshowitz, 1997; Jarvenpaa and Leidner, 1999; Kock, 2000). In the event of a tsunami, tsunami warning system managers must assemble effective, functioning response organizations in periods of less than 24 hours and then adjust the organizational structure to the needs of the response (Tuler, 1988; Bigley and Roberts, 2001). A challenge for tsunami warning systems is therefore to develop effective organizational structures that provide reliable and sustainable operations in non-tsunami periods as well as during catastrophic incidents. HROs typically have flexible and redundant organizational structures that permit organizational slack, allow testing of different response modes and techniques, and provide members the opportunity to develop communication, decision mak- ing, and organizational culture that are essential to cooperative, interdependent operations ( Weick, 1987; Weick et al., 1999). Organizational structures that provide back-up, redundancy, skill overlap, checks and balances, and one-over-one reviews are critical to the development of effective HROs (Grabowski and Roberts, 1997, 1999; Jarvenpaa and Leidner, 1999), and are thus key structures for highly reliable tsunami operations. Both structures and actors need to be tested regularly in rehearsal and simulation of tsunami events because tsunamis are relatively rare. Such regular rehearsals prevent the potential loss of institutional memory about appropri- ate organizational response. During this review, the committee found the current organizational structure—two TWCs managed by distinct regional weather service offices—associated with several benefits and risks: 

OCR for page 163
Long-Term Reliability and Sustainability of Warning Center Operations Benefits • Having independent research and development efforts at the two centers increases the competition and the potential for innovative approaches developed at either center. • If identical IT systems, software, and analytical methods were used, then the two centers would offer redundancy in the system, which is especially important given that each center’s location is vulnerable to natural hazards. • If identical IT systems, software, and analytical methods were used, then the two centers could leverage resources for IT development and modernization. • Having two centers in regions that are at great risk of tsunamis offers opportunities to engage with and to educate the emergency management community, the public, and media. Risks • Because the two TWCs are managed by two different regional NWS offices, the two centers display different organizational cultures. • Two centers with distinct AORs and different message thresholds greatly increase the potential for confusion and hampers effective decision making during an emergency. • The current geographic separation in the AOR is not intuitive and can result in difficul- ties with regard to interpreting who is under a tsunami warning or not. • The current physical settings and the organizational structure within the NWS pro- vides minimal integration with the tsunami and earthquake research community or other operational forecast and warning centers within NOAA (e.g., all other centers are managed by NCEP). • Because both the TWCs are located in remote locations, and neither is co-located at another NOAA, seismic or mission-critical center, opportunities to leverage lessons learned and best practices and to adopt standard processes and procedures are limited. • NOAA’s already limited technical, professional, and economic resources are stretched to support both centers’ infrastructure, IT, and engineering maintenance and upgrades. • aintaining and modernizing software and hardware systems is difficult because of M limited staffing support. Because the TWCs are currently not operationally redundant, they lack the benefit from effectively leveraging limited staff resources (e.g., they must hire more highly specialized IT personnel to update both systems simultaneously). • Supporting two robust and redundant communication networks incurs additional expenses. • The two TWCs are designed to be back-ups for each other, but they do not operate as such, creating an illusion of redundancy that could prove dangerous and costly, because adequate resources may not have been deployed to provide needed back-up and redundancy. 

OCR for page 163
T S U N A M I WA R N I N G S A N D P R E PA R E D N E S S Ideally, the TWC organizational structures allow for distributed groups of scientists to manage their joint processes, work together effectively in support of their shared mission, and avoid unnecessary redundancy. Support for TWC functions can be provided within an HRO framework, which opens several options for organizational structures. As described above, there are many differences between the centers’ operations, technology infrastructure, and human resources. The incompatibilities in the technology infrastructure run counter to the goal of redundancy in operations. In fact, the inconsistencies in outcomes and messages reduce the benefit of having two centers provide redundancy. Although the TWC organizational struc- tures could permit some organizational redundancy, that redundancy can cause difficulties if duplicate tasks are executed in geographically dispersed operational settings by organizational members who follow different procedures, use different warning thresholds, and communicate inconsistent messages to a public within confusing AORs. Conclusion: The goal of the current geographically distributed organization of the TWCs is to provide the system with back-up in the case of critical failure at the other center. However, based on the June 14, 2005, event analysis, the review of the literature on high- reliability organizations, and the current geographically distinct boundaries in AORs, the committee concludes that this redundancy is currently more likely to cause confusion than provide benefits. In addition, because the centers are under different management, use different analytical software and hardware, and appear to have distinct organizational cultures, the committee concludes that they function as separate rather than redundant systems. Conclusion: Even if the IT convergence plan is fully executed, the issues arising from producing different products and messages remain and increase the risk of confusing the public and state and local emergency managers. Conclusion: The current organizational model is problematic and reduces the ability of the TWCs to provide timely, accurate, and consistent warning products. The committee concludes that significant changes would need to occur in the manage- ment, operations, software and hardware architecture, and organizational culture for the two T WCs to become functionally redundant systems. As a result, the committee discussed alterna- tive organizational options, in addition to the TWCs’ current organizational structure: (1) Based on the committee’s assessment of the relatively slow transition and incorpora- tion of research advances into operations at both TWCs (see Chapters 3 and 4), the committee recognizes various benefits from co-locating the two centers (or a center) with other academic or scientific institutions or with other centers responsible for de- tection and warning (e.g., NCEP, the NEIC, PMEL, etc). For example, NCEP is co-located with the research community to increase the exchange of ideas between the scientific and operational staff. Alternatively, colocating the TWC(s) with the NEIC would give 

OCR for page 163
Long-Term Reliability and Sustainability of Warning Center Operations NOAA access to seismological expertise at this operational center run by the USGS and would pair the critical assets of two agencies with complementary missions. (2) Alternatively, because of issues arising from parallel or inconsistent procedures and potential confusion in the public from different warning products from the two centers, the committee suggests that a centrally managed center located in a single geographic location (such as the Hurricane Center) is a potential solution to the incon- sistency in methods, architecture, culture, and messages. A single center might also allow limited resources to be pooled and might ease the difficulties in 24/7 staffing of the centers. There are many current examples of highly reliable, mission-critical, large-scale systems that support real-time distributed operations using various organizational forms across a broad geographical area. In the NOAA/NWS community, these include the NWS Hurricane Center, the Severe Storm Lab, and the Storm Prediction Center at NCEP. There are other examples outside NOAA including the seismic, oceanographic, meteorological, undersea, cyberspace, and space systems communities, for example (National Aeronautics and Space Administration, 2005; National Science Foundation, 2006). Each of these HROs provide opportunities to leverage lessons learned and best practices for distributed tsunami warning operations. Recommendation: Organizational structures for the two TWCs should be evaluated and fully described as part of the enterprise-wise technology planning effort previously described. Whether there should be a single or multiple TWCs, or whether the TWC operations should be consolidated in a different location, should be addressed in the enterprise-wide, long-range planning effort. In evaluating the TWC organizational structure and locale(s), consideration should be given to the proximity to the research community, its user community, and the vulnerability to hazards. HROs achieve high levels of performance when their organizational structures support the decision making, communications, organizational culture(s), and trust required for success, and facilitate provision of the requisite information and knowledge sources to system users, participants, and customers (Grabowski and Roberts, 1999; Bigley and Roberts, 2001). Although developing a strong, unified organizational culture in a warning system can be difficult when members are geographically dispersed, (Grabowski et al., 2007), it is crucial in order to avoid dysfunctionality and miscommunication (Porter, 1993; Stephenson, 1995). CONCLUSIONS Effective tsunami detection, warning, and preparedness require that multiple, distributed tasks that are linked together to achieve the goal of reducing loss of life and economic assets using common processes are supported by highly reliable, distributed information technology. In a tsunami event, all of the distributed efforts must come together to produce an effective response and function as if it were a single organization (Tuler, 1988; Bigley and Roberts, 2001). 

OCR for page 163
T S U N A M I WA R N I N G S A N D P R E PA R E D N E S S In addition, tsunami warning and preparedness efforts must develop effective organizational structures that provide reliable and sustainable operations in non-tsunami periods, especially given the short time available to respond in a crisis (only minutes in the case of a near-field tsunami). Maintaining awareness in such a rapidly evolving crisis (i.e., situational awareness) poses a major challenge. The committee found that personnel at the TWCs are highly committed to the TWC func- tions, from detection through community outreach. TWC management and staff are highly supportive of the organization’s missions and are articulate advocates for the importance of the mission and TWC functions. The TWC mission is well understood by TWC management and staff, is clearly communicated throughout the tsunami warning system, and is well docu- mented. TWC personnel were found to be knowledgeable and effective in providing TWC func- tions, systems, and operations. However, aside from notable motivation and good communica- tion, the committee found many shortcomings of the TWCs in terms of functions, technology, human capital, organizational structures, and, as a result, many opportunities for significant improvements of the centers’ operations. The most fundamental changes required are an improved organizational model and an organizational culture that fosters expectations of performance excellence, and consistently measures and rewards that performance across the tsunami warning system. If the organiza- tional structures are adjusted to meet the required characteristics of an HRO, the TWC(s) could provide the function of an incident command center (ICC). Its central role as such an ICC would be to maintain situational awareness during a tsunami event, continuously updating its threat assessment, understanding the time horizon for informing critical decisions of the emergency management community, repeatedly informing critical users (public officials, emergency man- agers, media, etc.) of the evolving threat assessment, and monitoring the information broad- cast in the public arena to correct misinformation. At the same time that an improved TWC structure could function as the ICC during crisis mode, an improved tsunami program could provide long-term strategic planning and guid- ance, support for preparedness efforts, and coordination and support for educational efforts to ensure consistent content in the educational materials. If the TWCs become well integrated with other components of the tsunami program, assets at the TWCs could be used to more rapidly transition research at other program units into operational use. As previously discussed, a critical goal of the Tsunami Program should be to ensure that staffing and funding resources are allocated appropriately. Conclusion: An organizational culture change is needed within the NOAA/NWS Tsunami Program that supports and celebrates operational excellence; adopts national and international standards, processes, best practices, and lessons learned for all functions, technologies, processes, and products; and engages in ongoing, continuous process improvements. Conclusion: The committee found that the TWCs do not sufficiently engage in ongoing, joint or agency-wide, continuous process improvement activities for their functional, 0

OCR for page 163
Long-Term Reliability and Sustainability of Warning Center Operations technological, organizational, or human capital initiatives, such as those followed by other high-reliability, safety-critical distributed systems. Such activities provide critical benchmarks against which to measure performance over time, and could provide opportunities to reward and incentivize desired performance and behavior across the tsunami warning system. Recommendation: NOAA/NWS and the TWCs should undertake ongoing, joint or NOAA- wide, continuous process improvement activities for their functional, technological, organizational, and human capital initiatives, including the following: • eveloping measures of performance and benchmarking individual, organizational, and d technical performance against industry and agency metrics, • dentifying areas for improvement, i • etting short- and long-term performance goals, s • eveloping reward and incentive systems for such goals, and d • elebrating TWC and agency accomplishments as performance improves, in order to c raise the level of TWC performance to that expected of a high-reliability organization. 

OCR for page 163