PNSN-PRO-001 - University of...

20
QA: No Page 1 of 20 PNSN-PRO-001 Revision 0 Seismic Network Operations Effective Date: April 25, 2011 Approvals: Preparer: Printed Name Signature Date PNSN Director: Printed Name Signature Date Functional Manager: Printed Name Signature Date

Transcript of PNSN-PRO-001 - University of...

Page 1: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 1 of 20

PNSN-PRO-001

Revision 0

Seismic Network Operations

Effective Date: April 25, 2011

Approvals:

Preparer:

Printed Name Signature Date

PNSN Director: Printed Name Signature Date

Functional Manager: Printed Name Signature Date

Page 2: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 2 of 20

TABLE OF CONTENTS Revision History ..............................................................................................................................3 1.0 Introduction.............................................................................................................................4 1.1 Purpose....................................................................................................................................4 1.2 Scope and Applicability..........................................................................................................4 1.3 Discussion ...............................................................................................................................4 2.0 Prerequisites............................................................................................................................4 3.0 Documents Needed .................................................................................................................5 4.0 Special Tools, Equipment, and Supplies.................................................................................5 5.0 Instructions..............................................................................................................................5 5.1 Overview of Network Operations...........................................................................................5 5.2 Operate, Check, and Maintain the Pacific Northwest Seismic Network ................................8 5.3 Record and Archive Seismic Ground Motion Data ..............................................................15 5.4 Process Recorded Seismic Data into an Earthquake Bulletin...............................................16 5.5 Procedures for Significant Events.........................................................................................19 6.0 Records .................................................................................................................................19 6.1 Documents and Files.............................................................................................................19 Attachment 1 – PNSN Shop Workflow Overview .....................................................................21 Attachment 2 – PNSN Equipment List........................................................................................23 Attachment 3 – PNSN Seismic Equipment Information .............................................................31 Attachment 4 – PNSN Pre Deployment Workflow Overview ....................................................35 Attachment 5 – PNSN Post Deployment Workflow Overview...................................................37 Attachment 6 – PNSN Tilt Testing Procedure.............................................................................39 Attachment 7 – Digital Field Station Log....................................................................................43 Attachment 8 – RT130 Field Service Sheet.................................................................................45 Attachment 9 – Checking Current Status of EarthWorm ............................................................47 Attachment 10 – PNSN SeisNetWatch Example ..........................................................................49 Attachment 11 – PNSN 2010 Station Status Example ..................................................................51 Attachment 12 – PNSN Current Station Status File ......................................................................53 Attachment 13 – PNSN Seisops Archive.......................................................................................57 Attachment 14 – PNSN Stnops Archive........................................................................................59 Attachment 15 – PNSN Seisops Email Actions ............................................................................61 Attachment 16 – QUACK Query Interface ...................................................................................65 Attachment 17 – QUACK Query Results Example.......................................................................67 Attachment 18 – QUACK Weekly Signal PDFs Example............................................................73 Attachment 19 – Duty Seismologist Daily Checklist ....................................................................75 Attachment 20 – Duty Seismologist Weekly Checklist.................................................................77 Attachment 21 – Routine Phase Picking........................................................................................79 Attachment 22 – PNSN Alert Event Actions.................................................................................81

Page 3: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 3 of 20

REVISION HISTORY

Revision Number

CN Number

Effective Date Description of Revision

0 04/25/2011 Initial issue.

Page 4: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 4 of 20

1.0 INTRODUCTION

1.1 Purpose

This procedure describes the process for seismic monitoring in order to establish a comprehensive and reproducible earthquake catalog for the Pacific Northwest region (including the states of Oregon and Washington) and data suitable for quantitative analysis of ground motions therein. “Network performance” and “catalog completeness” in this procedure refer to products that are sufficiently accurate in timing, amplitude, and detail that they may be used in the analyses prescribed by ANSS Performance Standards V2.7 and the Procedures for their assessment. Operational priorities include high confidence of recording large-amplitude strong motion recordings within densely urbanized areas west of the Cascade range, and within an area of special interest including 10 km of the Hanford site. Also prioritized is the minimization of conditions that could lead to permanent loss of strong or unusual event waveforms, and maintenance of a stable, well-trained staff committed to the Project objectives for the monitoring network.

1.2 Scope and Applicability

This procedure is applicable to PNSN personnel who are involved in seismic monitoring activities. Positions titles discussed in Section 5 below do not necessarily refer to specific job titles. They represent roles and may be assigned to trained individuals whose precise job title may differ.

1.3 Discussion

Ground motion data is collected by remotely operated seismographs and transmitted by both wireless and wire-borne telemetry to the Pacific Northwest Seismic Network at the University of Washington in Seattle. A seismic processing software application integrates the data from the remote seismograph systems. The data are processed in real-time for event identification and automatic event location and magnitude estimates. Preliminary locations and magnitudes developed by trained seismic analysts, and subsequently reviewed and finalized by a network seismologist, are the basis of the regional earthquake catalog. Any human made seismic events (blasts, mine-collapses, etc.) or significant non-earthquake ground shaking sources (avalanches, landslides, meteor impacts, etc.) will also be identified.

Digital and modern analog seismic stations and telemetry systems are complex electronic components of an integrated hardware/software real-time data processing environment. The systems require regular maintenance and oversight, a primary function of seismic network operations. The network has been designed to ensure minimum downtime and necessary redundancy in order to provide a reliable environment for recording all significant seismic events.

Page 5: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 5 of 20

2.0 PREREQUISITES

None

3.0 DOCUMENTS NEEDED

− USGS Circular 1188 Requirement for an Advanced National Seismic System − ANSS Performance Standards, Rev. 2.7 (Oct. 2008) − Guidelines for reporting Regional Seismic Network compliance with ANSS

Performance Standards V2.7 − USGS Open-File Report 02-92; Technical Guidelines for the Implementation of

the Advanced National Seismic System—Version 1.0 4.0 SPECIAL TOOLS, EQUIPMENT, AND SUPPLIES

− Seismic Dataloggers − Seismometers

− Accelerometers − Calibrated Digital Multimeter

− Seismic Network Communications System − Internet Packet Transmission Systems

− Data Acquisition and Processing Computers − Peripheral Storage Devices and Media

5.0 INSTRUCTIONS

The following work may be conducted in whatever order the work requires. For that reason, read the entire procedure and attachments before beginning work.

5.1 OVERVIEW OF NETWORK OPERATIONS

5.1.1 Network Seismologist:

A. Assign task responsibilities.

B. Monitor routine network operations activities. Monitoring will include the following.

− Frequent examination of SeisNetWatch. − Frequent examination of PNSN and ANSS Recent Earthquakes

webpages to ensure they are updating properly. − Reading daily system check e-mails to appraise any conditions that

may impact station amplitude and timing accuracy (data quality).

Page 6: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 6 of 20

− Ensuring that ANSS catalog transfer has taken place.

− Routine data management, systems maintenance, and network operations activities in support of this procedure.

C. Respond to conditions that arise during 24/7 network operations activities that may impact network performance and catalog completeness.

D. Document network monitoring activities described.

E. Maintain familiarity with scientific issues related to seismic activity in the region, present network results to various forums as necessary and appropriate, and evaluate whether network capabilities can be brought to bear on solutions to these issues.

F. Maintain a prioritized contact list in a readily accessible location that can be used by PNSN personnel in the event that off-hours problems in seismic network operations are encountered.

G. Maintain a list of individuals and organizations to notify in case of a significant earthquake. Maintain a guidance document developed for the purpose of informing other project participants, the news media, and the interested public following a significant earthquake.

5.1.2 Seismic Network Engineer (and Field Technician, as assistant):

A. Maintain and monitor remote data acquisition and telemetry systems and respond to conditions that could impact network performance and/or catalog completeness.

B. Correct conditions (5.1.2.A) independently or through coordination with network operations personnel, and/or schedule required or routine field maintenance activities as appropriate.

C. Monitor equipment malfunctions for trends that might allow for preventive maintenance.

D. Coordinate routine site visit activities with the Network Seismologist.

E. Notify the Network Seismologist and note in electronic logs (i.e. station “Shop Files”) actions taken to address conditions that could impact network performance and catalog completeness to include but not limited to:

− Site visits and actions taken. − Routine and preventative maintenance activities.

Page 7: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 7 of 20

5.1.3 Computer Administrator:

A. Maintain and monitor remote network infrastructure, backup systems, and telemetry systems and respond to conditions that could impact network performance and/or catalog completeness.

B. Correct conditions (5.1.3.A) independently or through coordination with network operations personnel, and/or schedule required or routine maintenance activities as appropriate.

C. Monitor computer network infrastructure for trends that might allow for preventive maintenance.

D. Coordinate computer network system maintenance, upgrades, and repair activities with the Network Seismologist and network operations staff.

E. Notify the Network Seismologist of actions taken to address conditions that could impact network performance and catalog completeness, to include but not limited to:

− Upgrades of network monitoring applications and capabilities.

− Routine and preventative maintenance/system-administration activities.

5.1.4 Seismic Analyst (and “Duty Seismologists”)

A. Perform routine analysis of seismic recordings to identify and locate earthquakes. Review automatic locations, revise phase arrival information as needed.

B. Maintain PNSN catalog and provide data for the production of PNSN reports as requested by the Network Seismologist.

5.1.5 Scientific Programmer (Software Engineer)

A. Maintains seismic network data processing programs.

− In consultation with the Network Seismologist and the Computer System Administrator, perform upgrades of network seismic data processing applications and capabilities.

− Monitor performance of seismic data processing programs. − In consultation with Network Seismologist and relevant ANSS

software committees, make code changes to data processing programs.

Page 8: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 8 of 20

B. Develop utility programming code as needed to carry out routine network maintenance tasks.

C. As directed by the Network Seismologist, adapt and configure code (including upgrades) to provide seismic network data and knowledge products.

− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and various notifications and alerts.

5.1.6 Seismic Network Records Technician

A. Maintain PNSN station metadata.

5.1.7 Seismic Network Document Librarian

A. Maintain and archive documents related to PNSN operations, including:

− “Real Estate” agreements, easements, and landowner agreements.

− Service contracts (i.e., Telemetry providers). − Warrantee and Guarantee information, purchasing documents.

5.1.8 Seismic Network Manager

A. Coordination of activities.

− Administrative responsibility

5.1.9 All Personnel:

A. Assure that at least one other person within PNSN is capable of performing your responsibilities, and keep that person informed about the status of your activities so that he/she could carry on your tasks without significant interruption in the event of your absence.

B. Coordinate travel or leave of absence with other personnel capable of, and jointly responsible for, performing your tasks, so that network operations will continue without interruption.

C. Report on conditions that might affect network performance and/or catalog completeness to the Network Seismologist, the Development Technician, the Computer Administrator, or others as appropriate.

Page 9: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 9 of 20

5.2 OPERATE, CHECK, AND MAINTAIN THE PACIFIC NORTHWEST SEISMIC NETWORK

5.2.1 Amplitude Checks

This section describes system checks performed to ensure that seismic monitoring instrumentation is operating as expected. These checks primarily, but not exclusively, check the response curve of the seismic sensor. There are three modes of system checks.

Pre-Deployment Checks are performed on dataloggers and accelerometers prior to installation. For dataloggers, see Attachment appropriate to the datalogger type and/or sensor type being deployed. Document pre-deployment checks on appropriate System Check Analysis Report.

Installation and Maintenance Checks are conducted during station installation and when a seismometer is adjusted or replaced. Installation and maintenance checks are specified in relevant Attachment, and documented in the appropriate System Check Analysis Report.

In-Service Checks are performed regularly to confirm system performance and track performance trends. In-Service Checks apply system check software routines or routines that have been validated against software routines recognized by ANSS as representing the national standard. In-service Checks are used to initiate preventative maintenance as required to assure performance within acceptance criteria (see relevant Attachments for appropriate equipment).”

NOTE: In some cases, sensors may not lend themselves to adjustment or repair, but are nevertheless of value for monitoring activities, and may require additional supporting information.

A. Seismic Engineer or Field Technician:

1. Perform Pre-Deployment Checks using appropriate Attachments.

2. Transmit completed Pre-Deployment Check results, at least annually, to records in accordance with Section 6.0.

B. Network Seismologist and Seismic Engineer or Field Technician:

1. Conduct Installation and Maintenance checks using appropriate attachments and document effort and result.

2. If sensor does not meet acceptance criteria, arrange replacement or repair.

3. Transmit completed Installation and Maintenance check results, at least annually, to records in accordance with Section 6.0.

Page 10: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 10 of 20

C. Network Seismologist and Seismic Records Technician:

1. Conduct In-Service Checks when maintenance activities could affect ground motion recording or when network personnel identify the time series as appearing abnormal.

2. Maintain In-Service Check results in electronic files within the seismic processing system.

3. Identify In-Service Check results that require preventative maintenance and notify the Seismic Engineer and/or Field Technician.

4. Document corrective actions taken to address sensor performance.

5.2.2 Time Checks

NOTE: The method of the timing check depends on telemetry and datalogger type. NOTE: Analog stations are recognized by their communication of ground motions as continuously variable signals for digitization at the UW in Seattle or at a number of remote digitizing stations (University of Oregon, Forks, Klamath Falls, Tacoma Emergency Operations Center, Lower Rattlesnake). A UTC (Coordinated Universal Time) code is also recorded as an analog signal at several sites. Analog data channels are time-stamped by the digitizer at the data center.

A. Analog Stations

1. Network Seismologist:

Within the seismic processing system, record on a data channel a sequence of pulses encoding absolute time, synchronized to Coordinated Universal Time as mirrored by NIST or the U.S. Naval Observatory.

2. Seismic Analyst:

During routine event analysis, identify a minute mark on the encoded time-series trace and confirm time accuracy within the seismic processing system. Notify Development Technician and the Network Seismologist of timing irregularities.

3. Network Seismologist:

Log times for which station time is inaccurate in the network electronic log. Notify seismic analysts. Station phase times during

Page 11: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 11 of 20

these time periods will not be used in developing earthquake locations.

B. Digital Stations

NOTE: Digital station timing is determined from a GPS time source and GPS receiver. A datalogger’s internal clock is synchronized to Coordinated Universal Time when a “GPS lock” is established. The datalogger time-stamps each data packet to its internal clock. The “GPS lock” status is received at the data center and archived. Seismic Engineer and Network Seismologist:

1. Monitor datalogger clock status for unreliable station timing. Such

conditions may include:

− “GPS lock” not reported − Irregular “GPS lock” reports

− Clock adjustments of greater than 10 ms

2. Log times for which station timing accuracy is unreliable. Seismic phases from these stations during these time periods will not be used for developing earthquake locations.

5.2.3 Polarity Checks

NOTE: Polarity of seismometers can only be “changed” by physical modification of the seismic sensor or cables during site maintenance activities. Seismic Analyst and Seismic Records Technician:

A. Check the channel polarity for datalogger/sensor systems as follows:

1. Following station installation.

2. Following station maintenance that could impact channel polarity.

B. Measure channel polarity at network stations from suitable teleseisms within the seismic processing system and document event date and time. For specific station checks required following installation/maintenance-impacts it is only necessary to confirm polarities at the impacted station.

C. Correct channel polarity in the station channel metadata as needed. Maintain polarity check results in the electronic log.

Page 12: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 12 of 20

5.2.4 Additional Instrument Checks

Seismic Records Technician and Seismic Analyst:

A. Monitor visual display of real-time data from remote seismic stations to assure visually the network is operational. Primary checks for station operation are conducted by seismic analysts during event reviews.

B. Notify the Seismic Engineer or Field Technician or Network Seismologist, as appropriate, of conditions that could impact network performance or catalog completeness.

5.2.5 End-Point Calibration

Seismic Engineer and/or Field Technician:

In the case of contract termination or of removal of data collection equipment, conduct final in-service checks on or near the last day of data collection.

5.2.6 Measuring and Test Equipment (M&TE) Calibration

Seismic Engineer:

A. Ensure the measuring and test equipment to be used in seismic network operations is calibrated by a qualified supplier.

B. Ensure a sufficient number of calibrated multimeters are available for field use at all times.

C. Inform the Network Seismologist of irregularities in M&TE calibrations that may impact data quality.

5.2.7 Determining Locations of Stations

NOTE: This section pertains to any personnel who determine the location of stations used for seismic monitoring activity.

Seismic Engineer or Field Technician:

A. Use a handheld GPS unit that has passed the GPS check within the past year. See Attachment N for guidance on checking GPS units.

B. Record GPS Check results in the electronic log.

C. Set the GPS unit to record coordinates in the WGS84 reference frame. Set the elevation coordinate readout to meters and the lat-lon readout to decimal degrees.

Page 13: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 13 of 20

D. After satellite lock and initial coordinate readout, allow the unit to run no less than 5 minutes, and then document the last position on the readout:

− Latitude − Longitude − Elevation.

E. Record location on the Station Installation report.

5.2.8 Establishing Seismograph Stations

A. Seismic Engineer or Field Technician, and Seismic Network Document Librarian:

1. Obtain station location and establish land-use authority for site access and any land disturbance activities.

2. Document station location and configuration and complete the appropriate Attachment for Station Installation. Transmit the completed report to records in accordance with Section 6.0.

B. Network Seismologist:

Include new station information on the appropriate Attachment for Station Installation, in the seismic processing system.

5.2.9 Portable Instrument Operation

NOTE: Following significant seismic events or in special circumstances, it may be necessary to supplement the regional monitoring network with portable seismograph stations. The need could arise because of the location of the event with respect to the existing network or the potential to record specific data regarding a scientific or engineering problem. Portables may also be deployed in pre-planned locations to address specific performance-confirmation issues. Portable seismographs may be configured with various datalogger and sensor types.

NOTE: If the portable instrument is being managed under a scientific notebook designated for specific scientific field investigation or details of an emergency earthquake response are not covered by this procedure, the usage is documented in the appropriate scientific notebook

A. Seismic Engineer and/or Field Technician:

1. Perform Pre-Deployment and Installation and Maintenance Checks when practical.

Page 14: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 14 of 20

2. Refer to appropriate Attachment for minimum information required for installing a portable instrument.

3. Conduct station maintenance periodically on stations whose status cannot be determined remotely.

4. Conduct the site visit using applicable elements of the relevant Attachments.

NOTE: If a site visit is conducted, only the measurement of system check voltages are considered important to safety.

a. Check that the station is physically intact and operational. Make a written note of any exceptional conditions such as indications of disturbance or non-operation.

b. Assess the accuracy of the date and time indicated. For stations with GPS timing, confirm that the GPS clock has been locking periodically.

c. Where periodic data recovery is required, stop data acquisition using an external datalogger control device. If the datalogger records to a removable media device, remove the data-bearing portable media (e.g., a compact flash card or external solid-state drive) and replace it with one having sufficient free space for data expected by the time of the next visit. Restart data acquisition and confirm acquisition start.

d. Maintain removable media in a safe environment and deliver it to the seismologist supervising the deployment.

B. Network Seismologist and Seismic Records Technician:

1. For new installations, enter portable station locations and datalogger and sensor metadata in the network database.

2. Use results of system checks to confirm expected calibration constants and ensure that they are entered correctly into the network database.

3. Receive data on compact flash media as it is recovered from site visits and after demobilizations.

4. Play back recorded data and integrate it into the network data archives.

Page 15: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 15 of 20

5. Use network-processing tools to view the recorded data for completeness, performance of the triggering (as applicable), performance of the datalogger and sensors, suitability of the data for its intended purpose, and the approximate total data recovery volume.

6. Upon confirming that the data are successfully integrated into the data archive, return the removable media to the Seismic Engineer and/or Field Technician for reformatting and re-use.

7. Submit the records in accordance with Section 6.0.

5.3 RECORD AND ARCHIVE SEISMIC GROUND MOTION DATA

NOTE: To maintain effective seismic network operations, certain regular (daily to seasonal) operational checks and activities are required at the network operations center as described in this section.

1. Computer Administrator:

A. Establish capabilities for cell phone paging/messaging and/or e-mail notification to network operations staff in the event of potential computer system and/or telemetry system malfunction.

B. Maintain the internal computer network, data collection computer systems, and data storage media to assure data from field recorders is transferred to data storage locations for archive and analysis.

C. Maintain control of electronic media following the guidance in the relevant Attachment.

D. Maintain current licenses of commercial software and current maintenance contracts for computers as appropriate.

2. Seismic Engineer and/or Field Technician:

A. Observe telemetry alarm systems for indication of power outage or other system interruptions.

B. Check the stand-by generator to ensure that the “Gen. Ready” LED is on.

C. Observe real-time displays of stations from the seismic network and identify station and communication system irregularities. Notify Network Seismologist and take corrective actions as appropriate.

3. Network Seismologist:

Page 16: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 16 of 20

A. Examine time-series records from at least 20 seismic stations (vertical channels) located in different geographic parts of the network coverage area daily as 24-hour image displays (helicorders). Request corrective action of appropriate personnel as needed.

B. Review output from various scripts and assessment tools (SeisNetWatch, Morning Report, IRIS’ Quack Report, SMO Daily Report) to assess overall seismic network downtime and its potential impact on the completeness of the earthquake catalog.

C. Review station “noise” characteristics as revealed by the PDFs at the IRIS DMC BUD system to detect changes in individual station performance that might affect network detection capabilities.

D. Prepare and submit reports to ANSS following the ANSS guidelines to demonstrate compliance with the V2.7 ANSS Performance Guidelines.

4. Network Records Technician:

A. Maintain duplicate DVD backups of data collected within the seismic network, including daily database records generated within the seismic processing system.

B. Store DVDs in secure and separate locations.

5.4 PROCESS RECORDED SEISMIC DATA INTO AN EARTHQUAKE BULLETIN

5.4.1 Seismic Event Records

Network Seismologist:

A. Maintain a record of station locations, station configurations, and sensor response information in an electronic file(s) within the seismic processing system.

B. Implement an automatic seismic event location and magnitude determination process within the seismic processing system.

1. Review notable or significant events, and evaluate whether response to significant events is required. See section 5.5 for significant event procedure

2. Provide automatic event location information upon request to relevant state and federal agencies, and to the general public in the form of email, text messages, and/or web postings.

C. Assign the following responsibilities to seismic analysts, and manage routine processing of seismic events.

Page 17: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 17 of 20

1. Determine preliminary seismic event locations and magnitudes using data from the seismic network. Use relevant attachments on Guidance for Determining Preliminary Event Locations and Magnitudes.

2. Maintain the electronic record of seismic events in the seismic processing system.

D. In consultation with PNSN clients (NEIC, CVO, DOE/MSA, etc.) determine catalog magnitude and location completeness targets within geographical subsets of the network coverage area.

E. Review preliminary event locations of all earthquakes meeting the geographic and magnitude conditions for the authoritative catalog.

1. Relocate seismic events if phase arrival times or polarities are modified during event review.

2. Compile reviewed event parameters (origin time, latitude, longitude, depth, and magnitude) with relevant location uncertainties in the seismic processing system.

3. Maintain seismic waveform data and phase arrival times associated with reviewed seismic events within the seismic processing system.

F. Submit the authoritative catalog from section 5.4.1.E to the ANSS national catalog at least daily. Include:

− Seismic event locations and origin times − Location and origin time uncertainties

− Magnitudes − Event types

G. Transmit the combined final catalog of event locations and magnitudes resulting from reviews under 5.4.1.C,D,&E, to any other clients as required.

H. At least annually, transmit an electronic file(s) of station locations, station configurations, and sensor response information in formats described in the seismic processing system documentation to the ANSS.

I. Verify electronic data transfers and document them to ensure data integrity. For automated data transfers associated within network operations, manual verification is impractical. For this data, document procedural controls on the transfer processes in the scientific notebook.

Page 18: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 18 of 20

5.4.2 Review of Data

A. Network Seismologist:

1. Select a Technical Reviewer who is independent of the work to be reviewed.

2. Compile a review package that contains the following:

− A copy of the data, including electronic media − Any pertinent background information (e.g., reports,

scientific notebook entries, documentation associated with the data)

− Data Review Checklist

3. Forward the review package to the reviewers.

B. Technical Reviewers:

1. Review the data and associated documentation using the criteria identified on the Data Review Checklist.

2. Document comments on the Data Review Checklist.

3. Forward the completed Data Review Checklist to the Network Seismologist for resolution of comments.

C. Network Seismologist:

1. Resolve the comments and document responses on the Data Review Checklist.

2. Incorporate any changes in the data and associated documentation.

3. Forward the revised data and associated documents, and the Data Review Checklist to the reviewers.

D. Technical Reviewers:

1. Review the documentation to ensure comments responses are acceptable and that comments have been incorporated.

2. Document and submit any additional comments if necessary.

3. Escalate any comments that cannot be resolved to successively higher levels of management until resolved.

Page 19: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 19 of 20

4. Once comments are resolved, sign and date the Data Review Checklist, and forward it to the Network Seismologist.

E. Network Seismologist:

Submit records in accordance with Section 6.0.

5.5 PROCEDURES FOR SIGNIFICANT EVENTS

5.5.1 Significant Events

A. Network Seismologist:

1. In consultation with PNSN clients, and in accordance with ANSS Performance Standards V2.7, determine earthquake geographic locations and magnitudes to be recognized automatically as “significant events”.

2. A significant event that is detected automatically or during review by the seismic analyst or duty seismologist (also called an “alert event”) should trigger an series of alarm notifications and actions. The actions to be taken are decided by the Network Seismologist, and are elaborated on in the relevant attachment.

3. Among the actions triggered by an alert or significant event are the creation of a number of “products”, including: ShakeMaps, Community Internet Intensity Maps, fault plane solutions, Moment Tensor, and Notable Earthquake Webpages. Alert event notifications are sent to Emergency Managers as appropriate. These

4. Events not recognized by the rules defined in 5.5.1.A.1&2 as significant, may nevertheless be deemed to be so (examples: volcanic unrest, swarms, and events generating public and/or press interest). The Network Seismologist should decide when an event should be considered actionably significant.

6.0 RECORDS

The documents and/or electronic files listed in Subsection 6.1 shall be collected and maintained as individual records or included in a records package, as specified.

6.1 Documents and files

Instrumentation Records Package: − Datalogger Pre-Deployment Check Reports − Accelerometer Pre-Deployment Check Reports

Page 20: PNSN-PRO-001 - University of Washingtonearthweb.ess.washington.edu/pbodin/PNSN/PNSN-PRO-001.Rev0.pdf− PNSN products include: ShakeMap, FPFIT, ShakeCast, TMTS2, Swarmon, REQ2, and

QA: No Page 20 of 20

− Installation and Maintenance Check Reports − Station Installation Reports − Checklist for Portable Station Site Visit − Network operations electronic log (“Shop File”) − Data Review Checklists

Operations Records Package: − Seismic event review sheets for events from Section 5.4.1.D. − Catalog locations, magnitudes, and phase arrival times for earthquakes.

Records submitted in:

− Seismic catalog − Catalog metadata (as “Dataless Seed” )

Attachments Follow