Guidelines for Discharge Instrument Verification and

Page 1 of 85

Guidelines

for Conducting and Reporting on

the Verification and Calibration of

Performance of Discharge Measurement Instruments

Draft March 2012

Patrick J. McCurry, P. Eng Project Team Member

CHy Project X: The Assessment of the Performance of Discharge Measurement Technologies and Techniques

Page 2 of 85

Table of Contents

Introduction …………………………………………………………………….……………….…………. 3 A1) Protocols/specifications for Performance Verification ……..….…..………………….. 3

Performance Specifications ………………………………..……..……….……………….. 3 Instrument Performance Elements ….………………….……….………………… 3

Performance Verification ……………………………………………………………………… 4 Verification Testing …………………………………………….………………………………. 4

Approach A …………………………….………………...………………………………… 4 Approach B …………………………………………….…………………………………… 5

A2) Protocols for Instrument Calibration ………………………….…………………..…………. 5 Water Level Sensors ……………………………………………………………………….….. 5 Traditional Current Meters ………………………………………………………………….. 6 Acoustic Doppler Velocity Meters …………………………………………………………. 6

B) Reporting on Instrument Verification and Calibration Results …,…………………….. 7 Definitions ………………………………………………………………………………………………….… 8 Document History ……..………………………………………………………….………………………. 9

Appendices Appendix 1: Example Performance Specifications for EDAS Data Logger … 11 Appendix 2: Example Performance Specifications for ADCP ……...……..……. 20 Appendix 3: Example of a Qualification Test Procedure for Electronic Data

Acquisition System (EDAS) Data Logger ……………………….. 29 Appendix 4: List of References Related to Use of Hydroacoustic

Technologies in Moving-Boat Flow Measurements as posted on the USGS OSW Hydroacoustics Website .......... 55

Appendix 5: Example Reports on Instrument Testing and Comparison By NHS’s ……………………………………………………………..….… 58

Appendix 6: Example Report on Verification of Performance as per Manufacturers Stated Specifications …………………….……… 59

Appendix 7: Examples of Water Level Sensor Calibration Procedures ….…… 60 Appendix 8: Examples of Calibration Protocols for Vertical

Axis Current Meters ………………………………………………….. 61 Appendix 9: Example Procedures for Checking Calibration of

Acoustic Doppler Instruments ………………………………….. 68

Page 3 of 85

Introduction Under the WMO Project “Assessment of the Performance of Flow Measurement Instruments and Techniques”, task number 4 is the development of guidelines for conducting and reporting results of flow instrumentation calibration and performance tests on instruments and techniques. Two specific sub-tasks are:

a) Establishment of protocols/specifications for 1) instrument testing and verification of performance

characteristics and 2) calibration of instruments; b) Develop sample formats for reporting the data and results from testing, verification and calibration.

Subsequent to the creation of this task, the working group clarified its expectations to focus on field measurement instruments used to determine flow (including water level sensors, velocity meters, depth sensors, current profilers), and to have the documentation be very general guidance in nature. The goal is to allow NHS’s to share and compare the results of their testing, while accepting that each NHS has its own instrument needs, testing methodologies, performance specifications/standards, and internal reporting requirements. A1) PROTOCOLS/SPECIFICATIONS FOR PERFORMANCE VERIFICATION In order to establish protocols for verifying the performance of equipment or instruments that a NHS uses in its program, there must be an understanding of what the instrument is to deliver and how it will do that. The NHS must also know how it will be used and under what conditions. With this information, the NHS will have a better idea of the functionality expectations for an instrument, and from that, can establish ”performance specifications” that details the elements of importance for meeting the operational needs and standards of the NHS. For the purposes of this report, the definition of verification is as noted in the Definitions page at the end of the report. Performance Specifications Instrument performance specifications can be captured in three main categories: accuracy/precision, technical, and environmental. Performance specifications for any type of instrument – data loggers, pressure transducers, shaft encoders, ADVs, ADCPs, etc - can be developed by drawing from the elements listed below as appropriate for the type of instrument. The elements can then be noted as mandatory or non-mandatory, by which is meant those elements that the instrument must have versus those that are nice-to-have or might allow for additional consideration in the evaluation and procurement process due to added features for a similar price. See Appendix 1 for an example of a NHS data logger specification, Appendix 2 for an example of a NHS acoustic Doppler profiler specification. Instrument Performance Elements:

Accuracy/Precision: • Accuracy • Resolution • Conversion • Range • Drift • Response Time • Clock Accuracy • Data Acquisition Integrity/Quality Assurance/Quality Control Routines

Technical:

• Power Requirements • Electromagnetic Interference • Surge Protection, Transient Voltages and Currents • Memory Protection and EPROM Write Life • Programming Interface, Firmware and Software, Upgradability • Sensor Management • Data Storage • Data Handling

Page 4 of 85

• Output Data • Telecommunications • Satellite Transmitting Antenna • Input/Output Ports • Connectors & Cables • Shaft Encoder Float Pulley Assembly

o Shaft Diameter o Shaft Rotation & Starting Torque

Environmental

• Operating Temperatures • Relative Humidity & Moisture • Thermal and Mechanical Shock (transportation & storage) • Vibration • Solar Radiation (for outdoor mounted equipment) • Wind (for outdoor mounted equipment) • Sand & Dust • Ice Accreditation • Corrosion Protection

Performance Verification Using instrument performance specifications plus established in-house, national, and/or international standards for data collection, quality control, and product output, protocols can be developed to allow for testing an instrument to verify that it meets performance expectations. There are a couple of approaches that a NHS can take in this regard:

A) conduct testing to verify that the instrument meets the NHS in-house performance specifications; B) conduct testing to verify that the instrument meets the manufacturer’s stated specifications.

For Approach A, successful verification of meeting the NHS specifications gives the NHS the knowledge that an instrument will meet its program needs and minimizes the need to make major changes to established procedures/protocols when incorporating the instrument into its operations. For Approach B, successful verification of meeting the manufacturer’s stated specifications gives the NHS the confidence that an instrument will perform as stated by the manufacturer, but it will then be up to the NHS to decide whether such performance meets its program needs. With this approach, the NHS must realize that it is at the mercy of the manufacturers’ business decisions as to product functionality, and may have to be prepared to adapt some of its established procedures/protocols to accept a manufacturer’s business decisions on instrument performance if it is to incorporate such an instrument into its operations. Verification Testing Verification testing for Approaches A or B can be conducted in-house, or through other agencies or private sector companies equipped with the necessary equipment to perform the tests and attain the appropriate results. Approach A: For Approach A, using the in-house developed NHS performance specifications as a guide, detailed tests can be developed and used to verify the instrument as meeting the NHS functionality specifications. These tests should simulate actual operational conditions to the extent possible, including any unusual or unique conditions that may be encountered during operation (e.g. temperature/humidity/power conditions, smooth roll-over for leap year; specific mathematical operations for QA/QC, etc). See Appendix 3 for an example test procedure to verify data logger performance against the NHS specification for a data logger as given in Appendix 1. For some new technologies, such as acoustic Doppler instruments, performance verification is much more complex. Selected performance elements as suggested above can be easily verified through simple tests, while others, especially those related to the soundness of the measured and calculated parameters (e.g. depth,

Page 5 of 85

velocity, discharge) require significant and ongoing investment in time, effort, and bilateral discussions with the manufacturers and other instrument users. For some new technologies, which are replacing long established technologies (e.g. ADCP versus mechanical current meters), the verification of the performance is often demonstrated theoretically, but for the NHS practitioner, physical verification is usually required, often through comparison against the establish technology, and between various models of new technologies. Typically this is done with a strong degree of control in the procedure to ensure consistency and repeatability, and can be done in man-made environments, such as tow tanks, or in natural settings where each instrument being tested is subjected to the same conditions (e.g. in instrument “regattas”). Given the relative newness of acoustic Doppler technologies in riverine environments, NHS’s around the globe have spent significant effort exploring different ways to verify and validate this technology, and the standardization of procedures is elusive. However, there is growing communication between NHS’s for the exchange of information, such as testing procedures and results, through user forums, conferences hosted by manufacturers, and a very popular website hosted by the USGS Office of Surface Water (http://il.water.usgs.gov/adcp/), where much information is available to the global community. Appendix 4 contains a list of references available on that site related to the verification, validation, and use of hydroacoustic technologies in moving-boat flow measurements. Appendix 5 contains several documents from the Water Survey of Canada and the USGS that illustrates the variety of work done in recent years. Approach B: For Approach B, the testing agency should have a set of guidelines that is adaptable to a variety of instruments, so as to properly and fully test the instruments according to all of the individual manufacturer’s stated performance. The USGS Hydrologic Instrumentation Facility (HIF) is one agency that conducts instrument testing similar to Approach B. Its regularly issued reports on the results of its testing serve as a guide for in-house personnel and other users in knowing whether an instrument performs as stated by the manufacturer. As sample of such a report is given in Appendix 6. In the private sector, there is a global initiative underway for environmental technology verification (ETV), presently involving Canada, the USA, South Korea, and Europe (see www.etvcanada.com). This is a formal program whereby environmental technology is verified by licensed private sector companies as meeting the manufacturer’s stated performance, and a certificate is issued to that effect. In many areas of environmental data collection and problem mitigation, only products having a valid ETV certificate will be considered. It is recognized that the application of such a program to hydrological instrument performance is not within the mission of the ETV program, but it is envisioned that with some flexibility on the part of the ETV program, such a model could work for NHS instrumentation. A NHS could work with an ETV agency to develop protocols for selected performance elements that are not easily tested by a NHS due to the need for specialized equipment or conditions (e.g. extreme environmental conditions, power needs, accuracy deterioration due to aging of components, etc). If this approach could be realized, a NHS could simply state in its performance specifications that an instrument must meet, for example, “ETV Protocol XYZ for Extreme Climate Conditions” or “ETV Protocol ABC for Accuracy of the Instrument”. This would then puts the onus on the manufacturer to have the instrument’s performance for those elements verified by an ETV licensed tester, and no further work in that performance area would be required by the NHS when testing or procuring an instrument. A2) PROTOCOLS FOR INSTRUMENT CALIBRATION For the purposes of this report, the definition of calibration is as noted in the Definitions page at the end of the report. Water Level Sensors There are a variety of different sensors used to measure water level, including tape and weights, staff plates, shaft encoders, pressure transducers, ultrasonic, radar and lidar units to name a few. For tapes and weights and staff plates, any calibration is done using comparison to an independent measuring tool, and sometimes with adjustments made for temperature effects depending on the material of the tool. For the electronic/ultrasonic based instruments, they are initially calibrated by the manufacturer, the results of which typically accompany the unit upon delivery to the NHS for use as appropriate in their operations.

Page 6 of 85

Commonly, these units cannot be calibrated/recalibrated by the NHS, so if there is any reason to suspect the validity of the units’ results, they must be returned to the manufacturer for testing, repair, and recalibration. To assist NHS’s in ensuring confidence in the performance of the units and the validity of the readings, the NHS’s conduct regular field checks of the unit’s readings against an independent source (staff gauges, wire-weight gauges, etc). Any unexplained anomaly can be an alert to the potential need to recalibrate the sensor. Any sample docs to reference here? Appendix 7 Traditional Current Meters For the calibration of “traditional” velocity measurement technologies, the hydrologic community has well established guidelines in place. For example, mechanical current meters are typically calibrated in tow tanks under controlled and repeatable conditions, based on ISO 3455 Hydrometry – Calibration of Current Meters in Straight Open Tanks, 2007. There are a couple of approaches to the calibration of current meters, in that some agencies use a single standard rating equation for all of its meters, while other agencies determine individual rating equations for each meter. For example both the USGS and Water Survey of Canada use Price AA and Pygmy meters, but the USGS applies a standard equation to all meters while the Water Survey applies individual equations. A description of the USGS calibration procedures for vertical axis current meters in a tow tank is provided in Appendix 8a, and the rationale for the USGS decision to go with a standard equation approach is found in Appendix 8b. NHS’s generally have protocols in place regarding the need for periodic recalibration of current meters. Meters may be calibrated initially by the manufacturer or the NHS itself if they have access to tow tank facilities, and the resulting calibration table accompanies the meter to the buyer/user. Once the meter is in use, occasional recalibration at an acceptable tow tank facility is required if it has been used for a defined period (often 3 years), if it has been damaged, if parts are worn, or if results appear questionable. Some agencies, such as the Water Survey of Canada, have a policy that suspect meters be returned to the tow tank for an “as is” rating. This means the meter will be calibrated upon receipt before any repairs or adjustments are made, thus allowing for the salvage of measurements made using the defective meter. Additionally, there are strict procedures in place for in-field care and maintenance of current meters to minimize deviation from the calibrated state. These may include a daily air “spin test” of the meter propeller where the field hydrographer watches and listens for any irregularities that may retard the movement of the propeller, and takes the appropriate action as necessary. See Appendix 8c for the USGS “spin test” protocol. Acoustic Doppler Velocity Meters The use of acoustic Doppler technologies in the surface water quantity programs is a relatively recent development, and as such, there are few well defined procedures for calibrating these instruments available as yet. As with many of the water level sensors, acoustic units are delivered calibrated by the manufacturer, and any need for recalibration requires a return of the unit to the manufacturer. To minimize, and to identify, defective performance, NHS’s have worked with the instrument suppliers to build in software routines that check selected components for operation within set parameters, or the NHS’s have developed their own methods of checking for correct performance. These checks are a combination of selected diagnostic checks under controlled conditions, or in-field checks conducted prior to use, as routine maintenance, after use in rough conditions, or if results are suspect. They typically include checks for internal electronics, beam alignment and power, correction for moving bed bias (Loop Method), compass calibration, and temperature calibration. Appendices 9a, 9b, 9c, 9d and 9e describe several such checks, and Appendix 9f includes a list of USGS memorandums related to the use of hydroacoustic technologies. Other forms of in-field calibration checks may include “ADCP regattas”, where several units are used under controlled conditions, and the results compared. Such regattas may also include several different makes and models of acoustic Doppler instruments. In recent years, the USGS Hydroacoustic Working Group (HAWG) has been gathering the data collected in such events for future analysis of performance and uncertainty. Appendix 5a contains an example report, with procedures described in general, for regattas held by the Water Survey of Canada to compare a Sontek M9, a TRDI RiverRay, and a TRDI Rio Grande.

Page 7 of 85

B) REPORTING ON INSTRUMENT VERIFICATION AND CALIBRATION RESULTS It is recognized that individual NHS’s typically have internal guidelines for the production of reports, and this document is not meant to circumvent those guidelines. However, to enable the sharing of results across the hydrologic community at large and to facilitate the comparison of instrumentation, the following is suggested for consideration when writing those reports. Example reports for Approaches A and B can be found in Appendices 5 & 6.

Executive Summary • a brief description of the tested product(s), their purpose • a brief (high level) description of the test procedures and results

• include a statement on how the results compare to the NHS’s specifications/standards Objective and Approach of the Test • a short statement that summarizes the purpose of the test • a short narrative on how the test was conducted Description of Instrument(s) • details of the product, its purpose, how it operates • may include the manufacturer’s product specifications Test Procedures • details of the test procedures, including performance specifications being used • reference all instruments used as benchmarks for comparison, calibration Test Results • details on the findings, including how the instrument(s) performed against the NHS performance

specifications, against benchmark instruments, etc • include tables and graphs • test data and results to be stored in electronic format for sharing with other instrument users (format to

be established by Project X members?) Discussion of Results/Conclusions • non-technical narrative on the results – explanation of specific findings, reasons for non-typical product

performance • conclusions based on the initial objective of the test Related Observation/Comments • non-subjective statements on observations made on the product as part of the testing. References Appendices

Page 8 of 85

Definitions Verification and validation*, in engineering or quality management systems, it is the act of reviewing, inspecting or testing, in order to establish and document that a product, service or system meets regulatory or technical standards.

• Verification**: provision of objective evidence that a given item fulfils specific requirements**

• Validation**: verification, where the specific requirements are adequate for intended use**. It is sometimes said* that validation can be expressed by the query "Are you building the right thing?" and verification by "Are you building it right?" "Building the right thing" refers back to the user's needs, while "building it right" checks that the specifications are correctly implemented by the system. Calibration* is a comparison between measurements – one of known magnitude or correctness made or set with one device and another measurement made in as similar a way as possible with a second device*. The device with the known or assigned correctness is called the standard. The second device is the unit under test, test instrument, or any of several other names for the device being calibrated*. Instrument Calibration can be called for:

• with a new instrument • when a specified time period is elapsed • when a specified usage (operating hours) has elapsed • when an instrument has had a shock or vibration which potentially may have put it out of calibration • sudden changes in weather • whenever observations appear questionable

In general use, calibration is often regarded as including the process of adjusting the output or indication on a measurement instrument to agree with value of the applied standard, within a specified accuracy. For example, a thermometer could be calibrated so the error of indication or the correction is determined, and adjusted (e.g. via calibration constants) so that it shows the true temperature in Celsius at specific points on the scale. This is the perception of the instrument's end-user. However, very few instruments can be adjusted to exactly match the standards they are compared to. For the vast majority of calibrations, the calibration process is actually the comparison of an unknown to a known and recording the results. * Wikipedia on-line encyclopedia ** International Vocabulary of Metrology Acronyms ADV: acoustic Doppler velocity meter ADCP/aDcp: acoustic Doppler current profiler EDAS: Electronic Data Acquisition System ETV: Environmental Technology Verification GOES: Geostationary Operational Environmental Satellite GPS: Global Positioning System HIF: Hydrologic Instrumentation Facility (USGS) NESDIS: National Environmental Satellite, Data and Information Service (NOAA) NHS(s): National Hydrologic Service(s) NOAA: United States National Oceanic and Atmospheric Administration QA/QC: Quality Assurance/Quality Control SDI-12: Standard Digital Interface-1200 Baud USGS: United States Geological Survey

Page 9 of 85

Document History

Rev# Date State Description of Changes Draft 1 Aug 11,

2009 WMO Working Group Review

First draft created by P. McCurry for concept review and discussion by WMO Working Group on Assessment of Performance of Flow Measurement Instruments and Techniques.

Draft 2 Dec. 2011 WMO Working Group Review

Document reworked by P. McCurry as per comments received on Draft 1 from WMO Working Group.

Draft 3 Mar. 2012 WMO Working Group Review

Comments addressed from Draft 2 review and document expanded by to include a section on calibration, complete with appendices 7-9.

Page 10 of 85

APPENDICES

Page 11 of 85

Appendix 1

Example Performance Specifications for EDAS Data Logger*

* Used with the permission of the Water Survey of Canada, Environment Canada. Document based on 2004 data logger performance specifications, and may no longer be current.

1. ACCURACY & PRECISION - DATA LOGGER (NOTE: unless specified otherwise, elements apply to Levels 1 & 2 loggers)

(Note: in the following pages, Level 1 and Level 2 are used to differentiate degrees of logger performance) 1.1. Data Acquisition Integrity Routines

1. The DATA LOGGER MUST permit, by means of the PC, the initiation of sensor sampling

test cycle and the presentation of these results for analysis. 2. Acquisition, archiving routines SHALL not be interrupted during communications to

logger or sensor (via logger) via direct connect PC or telephone communications systems.

1.2. Clock Accuracy

• Level 1

• Level 2

1. Accuracy MUST be ±50 ppm per year. 1. For DATA LOGGER without GOES, accuracy MUST be ±50 ppm per year. 2. For DATA LOGGER with GOES, logger clock MUST be tuneable to GOES clock. 3. For DATA LOGGER with high data rate ( HDR ) GOES transmitter - the DATA LOGGER

clock MUST be synchronised to the HDR GOES transmitter. The HDR 1200 bps GOES transmitter clock MUST comply with NESDIS specifications for HDR GOES. The HDR 300 bps transmitter clock MUST meet the requirements of the 1200bps transmitter.

2. TECHNICAL SPECIFICATIONS - DATA LOGGER (NOTE: unless specified otherwise, elements apply to Levels 1 & 2 loggers) ( Referenced Military standards methodology will be used when testing for compliance is required) 2.1. Power Requirements

1. Normal operating voltage SHALL be 11 VDC to 15 VDC with over voltage levels up to 20

VDC. 2. Minimum cut-off voltage MUST be 10.75 VDC. 3. Power consumption, excluding sensors, SHALL not exceed 50 m Amps on average while

active and 10 m Amps on average while quiescent. 4. Power requirements of the instrument MUST be stated for all modes of operation and

SHALL be protected for over, under and reverse voltages. 5. During power interruptions, the DATA LOGGER MUST maintain correct time and date

references and resume logging when power returns to normal operational levels. 6. Backup batteries MUST support easy field replacement- not soldered in place.

2.2. Electromagnetic Interference

1. Equipment SHALL meet class A3 requirements of MIL-STD-461D for radiated emissions (RE102) and for radiated susceptibility (RS103).

2.3. Surge Protection, Transient Voltage and Current

1. The DATA LOGGER MUST withstand repeated power transients resulting from near lightning strikes.

2. Equipment SHALL conform to surge protection standards as detailed in ANSI standard C62.41 “Surge Protection in Low Voltage AC Power Circuits”, Class B.

3. Equipment SHALL not be affected by transient voltage and current originating from the power supply or other sources.

2.4. Memory Protection

and EPROM Memory life write expectancy

1. During primary power interruption, memory related to the operating program and data archive SHALL be protected to maintain correct time and date reference, programmed parameters and data, for a period of not less than 90 days

2. Remote access to programming and set-up parameters SHALL be password protected. 3. The write to EPROM memory SHALL operate properly for a minimum of 10 years based

on measurements at 5 minute intervals and 40 parameter changes per year.

Page 12 of 85

2.5. Programming Interface, Firmware and Software

1. The firmware that is resident in the DATA LOGGER MUST be upgradeable by PC using a method that does not require replacement of DATA LOGGER internal components.

2. All interaction with DATA LOGGER programs MUST be possible using a PC. 3. When using a PC, upload and download of parameter set-up sensor management, data

acquisition and retrieval SHALL be accomplished through menus or pop up windows. 4. Where applicable input of numeric information SHALL be in engineering units. 5. The DATA LOGGER SHALL revert to previously stored configuration if abnormal exit from

configuration routines occurs.

2.6. Sensor Management

• Level 1

Level 2

The DATA LOGGER SHALL be programmable with respect to how data from a sensor is acquired and processed. The DATA LOGGER SHALL have the following features as a minimum: 1. Capability to create, edit or delete sensor set-ups. 2. Data Acquisition:

1. Start time for data acquisition variable by sensor. 2. Acquisition frequency programmable from 1 per second to 1 per day.

3. Data Logging: 1. Log data with date and time stamp. 2. Logging frequency programmable from 1 per minute to 1 per day. 3. Ability to turn log on and off.

4. Maximum and/or minimum sensed values: 1. Determine values, programmable from 1 per minute to 1 per day. 2. Log value with date and time stamp of actual acquisition time ( to the nearest minute

) of the occurrence of max and/or min. 5. Alphanumeric sensor labelling ( 2 characters minimum length ). 6. Individual sensors independently programmable. 7. Position of decimal point variable by sensor. 8. Activation of a sensor (on/off designation). 9. Data download from user selectable date. 10. Provide for logging on PC or DATA LOGGER continuous live readings for user selectable

sensors with date, time stamp, and labels. 11. Data output via land-line MUST be individually selectable. 12. Direct access (transparent mode) to SDI-12 bus. 13. Capability of logging a minimum of 10 distinct parameters. 14. Easy input of conversion formulas for different sensors, i.e. temp. probes.

The following range of math instructions SHALL exist: Z = F Z = X add subtract multiply divide sqrt ln(X) eX xy π (Pi ) abs frac int mod sine cosine tangent minimum fifth order polynomial block move ,sliding block move min. max. avg spatial max spatial min spatial average mathematical functions are executed using the normal mathematical precedence. a minimum of 10 user defined equations of up to 120 characters per equation. Note: This does not exclude other math instructions

as above plus MUST have the following features as minimum. 1. Logging frequency programmable from 1 per second to 1 per day. 2. Maximum and/or minimum sensed values:

1. determine values, programmable from 1 per second to 1 per day; 2. log value with date and time stamp of actual acquisition time (to the nearest second)

of the occurrence of max and/or min. 3. Ability to acquire sensed data in time ordered, event ordered and gradient intervals. 4. Programmable alarm function (gradient and level ). SHALL also have the capability of

triggering a function (e.g. reading another sensor); 5. Data output via telemetry MUST be selectable

1. by parameter. 2. by occurrence (i.e. data collected at 15 minute intervals, only hourly values

transmitted). 6. Ability to run the logger in standard time with an option to offset for Co-ordinated

Universal Time ( UTC). 7. Capability of logging a minimum of 15 distinct parameters.

Page 13 of 85

8. User selectable warm-up time for a duration from one second to fifteen minutes for data acquisition by sensor parameter.

2.7. Data Storage

1. The DATA LOGGER MUST have a minimum of 200 days data storage for: 1. three (3) environmental parameters logged hourly, with one maximum and one

minimum per day, based on 5 minute samples of the sensor. 2. maintenance parameters logged once per day. 3. all of above complete with date and time stamp and data labels.

2. There MUST be a warning about potential memory erasure/data loss if user actions could result in such an occurrence.

3. Data overwrite when memory is full MUST be user selectable ( overwrite as default ).

2.8. Data Handling • Level 1

• Level 2

1. Logger MUST accept and store input data that may have up to 5 significant digits, with the

position of the decimal point variable by sensor. 2. All intermediate calculations MUST provide results equivalent to 32-bit long integer

architecture as a minimum, with a resolution at least one digit greater than the input data. 3. Data download :

1. The data that is resident in the DATA LOGGER MUST be downloadable by direct connect to a PC.

2. For data logged as per Data Storage item 2.7.1 the elapsed time of download SHALL not exceed ten minutes from start of download to resultant ASCII file stored on PC.

3. The resultant output MUST be in tabular or sequential ASCII format as described in Appendix 1.A.1.

4. The output MUST allow up to 7 digits as a minimum, including decimal point and sign, with the position of the decimal point variable by sensor.

4. Data Presentation: 1. MUST be in tabular or sequential ASCII format as described in Appendix 1.A.1. 2. MUST provide time series graphing of downloaded data as per Data Storage item

2.7.1: 1. minimum of 2 parameters simultaneously. 2. user selectable parameter versus time. 3. user selectable scale for individual parameters. 4. user selectable time interval by date.

as above plus: 1. replace item 2.8.level-1.2 above with: All intermediate calculations MUST provide results

equivalent to 32-bit IEEE 4-byte Real (Single Precision, Floating Point) as a minimum. 2. GOES satellite data ( conventional data rate and high data rate ) MUST be in ASCII

format as described in Appendix 1.A.2. 3. Data transmitted via GOES satellite ( not including HDR transmissions ) should be

centred in the assigned transmission window. ( examples 30 sec, 1 min, 2 min )

2.9.Telecommunications

1. DATA LOGGER firmware MUST support modem and GOES satellite telecommunications.

2. Telecommunications capability MUST be available as options to the logger, to be ordered as required.

3. Modem communications MUST be: 1. supported via supplier modems or third party modems; 2. via modems programmable up to at least 9600 baud.

4. For GOES satellite communications: 1. DATA LOGGER and transmitter (High Data Rate) MUST meet all criteria for GOES

(NOAA/NESDIS March 2000.); 2. DATA LOGGER MUST operate in random as well as self-timed transmission modes; 3. DATA LOGGER MUST perform timing tests, including present time, time to next

data acquisition and time to next transmission if integrated with self-timed transmitter, and single test transmission if integrated with random mode transmitter.

4. The GOES output message length MUST be truncated by the DATA LOGGER to prevent trip of the fail safe ( as per NESDIS High Data Rate specification )

5. GOES Satellite Transmitting Antenna: 1. transmitting antenna SHALL be to NESDIS specifications. 2. beam width SHALL be wide enough to include a pair of GOES satellites and SHALL

deliver the maximum possible power to reach both satellites. 3. Antenna MUST come complete with a 5m length antenna cable with appropriate

environmental connectors and antenna mounting hardware.

Page 14 of 85

2.10. Input / Output Ports • Level 1

• Level 2

DATA LOGGER unit MUST have: 1. RS232: 1 serial port; used for DATA LOGGER and sensor configuration and data

retrieval via direct connect PC or external data communications device, baud rate programmable up to at least 9600, compliant with RS232 standards.

2. SDI-12: 1 port (3 wire), minimum full SDI-12 capability using the latest (downward compatible) published version,

as above plus MUST have: 1. RS232: a second serial port identical to the above, with both ports individually

programmable (Note: If only one RS232 port is provided, the supplier MUST demonstrate how that one port can provide the same functionality, including that of element 1.1.2, that two separate ports would provide);

2. Event: 1 port, minimum 16 bit counter, 20ms closure, rollover or reset software selectable.

3. Analog: 2 differential configurable up to 4 single ended; resolution 1 bit or 0.025% full scale; analog to digital conversion minimum 12 bits (plus one sign bit); range ±5 volts DC and accuracy 0.1% full scale, temperature compensated over full range of operating temperatures. (Note: if voltage range input is less than ±5 volts, supplier MUST demonstrate how the above accuracy can be achieved).

4. Excitation: 2 ports, switched under software control, programmable from 0 to 5 V at 1% full scale resolution, accuracy at 0.1% full scale, range 0 to 5 volts DC, load compensated up to 20 m Amps; (Note: if voltage range output is less than ±5 volts, supplier MUST demonstrate how the above accuracy can be achieved).

5. Switched: one 12 VDC power output port to be used for sensor activation, that SHALL be enabled by software and SHALL have an output current of at least 750 m Amps.

2.11. Connectors

1. All connectors used for operation, maintenance, communication and sensor connection MUST be clearly labelled.

2. All connectors SHALL be equipped with a positive locking mechanism that will prevent inadvertent separation of the plug and socket.

3. All connectors containing a live wire end with the exception of the telephone RJ-11 MUST be female.

4. Sensor connection to the DATA LOGGER SHALL be by terminal strip or individual connectors or a combination thereof.

5. Insulation displacement connectors SHALL conform to the requirements of MIL-C-83503A.

2.12. Cables

• Level 1

• Level 2

1. A minimum 2.5 metre long power cable with appropriate connectors SHALL be supplied. 2. A minimum 1.5 metre long communication cable MUST be provided complete with a DB9

female connector on the computer end and an appropriate connector on the logger end. 3. If an external modem is supplied, a minimum 1.5 metre long communication cable

between the modem and logger MUST be provided, complete with the appropriate environmental connectors.

as above plus: 1. If satellite antenna is supplied, a minimum 4.5 metre antenna cable MUST be supplied,

complete with the appropriate environmental connectors. 2. If HDR transmitter and GPS antenna are supplied, a minimum 4.5 metre GPS antenna

cable MUST be supplied, complete with the appropriate environmental connectors.

2.13. Dimensions 1. The maximum size SHALL be 40 cm long x 40cm high x 35cm wide.

Page 15 of 85

3. ENVIRONMENTAL SPECIFICATIONS - DATA LOGGER ( Referenced Military standard methodology will be used when testing for compliance is required) 3.1. Operating Temperatures

1. Equipment SHALL operate through an ambient temperature range of -40°C to +50°C,

withstand temperatures from -60°C to +65°C and MUST automatically recommence normal operation when operating temperatures are achieved.

2. Cables SHALL remain flexible at -40°C (MUST not be brittle) and SHALL not deteriorate at +65°C.

3.2. Relative Humidity & Moisture

1. MUST withstand max. humidity 100% non condensing at 50°C & -40°C, min. humidity 3% at 50°C.

2. Casing MUST be water resistant.

3.3 Thermal and Mechanical Shock, (Transportation and Storage)

1. Equipment SHALL withstand instantaneous induced thermal shock during transport of 70°C (-50°C to +20°C) and SHALL operate under thermal shock of 15°C/min. for 2 minutes (-20°C to +10°C).

2. Equipment SHALL operate after experiencing a series of mechanical shocks equivalent to 18 impact shocks of 15g consisting of 3 shocks in each direction (6 total) applied to each of 3 mutually perpendicular axes of the equipment. Military Standard 810E, 516.4 (14 July 1989)

3.4. Vibration 1. Equipment SHALL withstand transportation vibrations 10 – 50 Hz without being in a

shipping container. Military Standard 167.

3.5. Solar Radiation (for outdoor mounted components)

1. Equipment and components SHALL: operate during periods of insolation intensity of 1022 W/m2; and ultra violet intensity of 64.5 W/m2; and withstand the effects of insolation intensity of 75.25 W/m2. Military Standard 810E, 505.3 (July 14, 1989)

3.6. Wind (for outdoor mounted components)

1. Equipment MUST withstand 5 second gusts up to 250 km/h and an average hourly wind speed of 160 km/h.

3.7. Sand & Dust

1. Sand and dust MUST not alter the operation of equipment.

3.8. Ice Accretion (for outdoor mounted components)

1. Equipment SHALL operate under icing conditions of 50mm thickness and specific gravity of 0.9, at winds as specified above. Military Standard 810E, 521.1 (14 July 1989)

3.9. Corrosion Protection 1. Corrosion resistant materials SHALL be used.

Page 16 of 85

Appendix 1.A: Data Presentation 1.A.1 Data Format: Telephone or Direct Connect Telephone or direct connect download format SHALL be identical to one of the two following formats: Format A (tabular) or Format B (sequential). Scenario: The instrument interrogates the sensor every 5 minutes, logs the value every 60 minutes and logs the maximum and minimum value (based on the 5 minutes readings) every 180 minutes. FORMAT A (tabular – space delimited)

Header section: Station identification : Free format Date column headers: Date, Time, Sensor code as defined by the data label, up to 8

characters, Sensor code , ..... Refer to column width and spacing as defined below.

Text: Dash (-) optional.

Data String section: Each column has the related values/format: Date: 2 formats required: yyyy/mm/dd and mm/dd/yyyy; Column width: 10.

(use of slash (/) or dash (-) as separators are permitted) Space: 1. Time: Format required: hh:mm:ss, Column width: 8.

Space: 4. Sensor value: 1) Value, ranging up to 7 digits as a minimum, including sign and

decimal point (variable position) (i.e. +or-#.###, +or-##.###, +or-###.##, etc.) in time ascending order.

2) Use of -999.99 or -9999.9 or -99999 to indicate missing data. 3) Max. and min. MUST be written in their related column and can

be written anywhere within the day. 4) Blank as required to complete column width of 10. 5) 1 space required between each sensor value column.

EXAMPLE FORMAT A (tabular – space delimited) \ Data from: Nechako River DATE: 11/20/1996 to 11/27/1996 \ | Header section DATE TIME VB HG / ---------- -------- ---------- ---------- / 11/20/1996 00:00:00 12.30 0.001 \ 00:05:00 -99999 0.001 \ 01:00:00 12.21 0.001 \ 02:00:00 12.20 0.001 \ 03:00:00 12.20 0.001 \ 03:05:00 -99999 0.001 \ 04:00:00 12.20 0.001 \ 05:00:00 12.20 0.001 \ 06:00:00 12.20 0.00 | 06:05:00 -99999 0.001 | 07:00:00 12.21 0.001 | Data String section 08:00:00 12.21 0.001 | 09:00:00 12.21 0.001 | 09:05:00 -99999 0.001 / 10:00:00 12.28 -99999 / 11:00:00 12.21 0.001 / 12:00:00 12.28 0.001 / 12:05:00 -99999 0.001 / 13:00:00 12.19 0.001

Page 17 of 85

13:55:00 -99999 5.917 14:00:00 12.19 5.885 15:00:00 12.28 5.832 16:00:00 12.28 5.858 17:00:00 12.20 5.771 17:10:00 -99999 5.887 17:55:00 -99999 5.669 18:00:00 12.25 5.788 18:35:00 -99999 5.657 19:00:00 12.28 5.797 20:00:00 12.28 5.718 20:30:00 -99999 5.810 21:00:00 12.20 5.685 22:00:00 12.10 5.859 23:00:00 12.10 5.726 23:30:00 -99999 5.642 11/21/1996 00:00:00 12.09 5.675 01:00:00 12.09 5.647 02:00:00 -99999 -99999 FORMAT A (tabular - comma delimited) Header section

Station identification : Free format Headers: Date, Time, Sensor code(s) as defined by the data label, up to 8 characters, comma delimited

Data String section: entries to be comma delimited

Date: 2 formats required: yyyy/mm/dd and mm/dd/yyyy. Time: Format required: hh:mm:ss Sensor value: 1) Value, variable position i.e. +or-#.###, +or-##.###, +or- ###.###, etc.. in time

ascending order. 2) Use of -999.99 or -9999.9 or -99999 to indicate missing/bad data.

DATA FROM: RID OTT DATE: 11/16/2000 to 11/17/2000 DATE,TIME,VB,HG 11/16/2000,00:00:00,14.01,2.800 11/16/2000,01:00:00,-99999,2.801 11/16/2000,02:00:00,-99999,2.801 11/16/2000,03:00:00,-99999,2.801 11/16/2000,04:00:00,-99999,2.801 11/16/2000,05:00:00,-99999,2.801 11/16/2000,06:00:00,-99999,2.801 11/16/2000,07:00:00,-99999,2.801 11/16/2000,08:00:00,-99999,2.802 11/16/2000,09:00:00,-99999,2.803 11/16/2000,09:30:00,-99999,2.955 11/16/2000,10:00:00,-99999,2.934 11/16/2000,11:00:00,-99999,2.892 11/16/2000,12:00:00,-99999,2.864 11/16/2000,13:00:00,-99999,2.847 11/16/2000,14:00:00,-99999,2.834 11/16/2000,15:00:00,-99999,2.825 11/16/2000,16:00:00,-99999,2.820 11/16/2000,17:00:00,-99999,2.817 11/16/2000,18:00:00,-99999,2.814 11/16/2000,19:00:00,-99999,2.816 11/16/2000,20:00:00,-99999,2.821 11/16/2000,21:00:00,-99999,2.830 11/16/2000,22:00:00,-99999,2.834 11/16/2000,23:00:00,-99999,2.837 11/17/2000,00:00:00,14.01,2.838

Page 18 of 85

11/17/2000,01:00:00,-99999,2.838 11/17/2000,02:00:00,-99999,2.837 11/17/2000,03:00:00,-99999,2.834 11/17/2000,04:00:00,-99999,2.833 11/17/2000,05:00:00,-99999,2.831 11/17/2000,06:00:00,-99999,2.827 11/17/2000,07:00:00,-99999,2.825 11/17/2000,08:00:00,-99999,2.822 11/17/2000,09:00:00,-99999,2.820 11/17/2000,10:00:00,-99999,2.818 11/17/2000,11:00:00,-99999,2.816 11/17/2000,12:00:00,-99999,2.814 FORMAT B (sequential) Header section: Station identification : Free format Data String section:

Date identification is required at the beginning of each day. Space: 2. Delimiter: Forward slash (/) or comma (,). Date: 2 formats required: yyyy/mm/dd and mm/dd/yyyy; Column width: 10.

(use of slash (/) or dash (-) as separators are permitted), Delimiter: Forward slash (/) or comma (,).

Text: 10 alphanumeric characters, optional. Each row to have the complete information on sensor code, value and time.

Sensor code: As defined by the data label, up to 8 characters, blank as required to complete column width of 10.

Delimiter: Forward slash (/) or comma (,). Sensor value: 1) Value, up to 7 digits as a minimum, including sign and decimal point

(variable position) (i.e. +or-##.###, +or-###.##, +or-####.#, etc.) in time ascending order, right justified to the delimiter, blank as required to complete column width of 12.

2) -999.99 or -9999.9 or -99999 indicates missing data. 3) Max. and min. can be written anywhere within the day. Delimiter: Forward slash (/) or comma (,). Time: Format required: hh:mm:ss, column width: 8. EXAMPLE FORMAT B Data from: Nechako River DATE: 1996-11-21 to 1996-11-27 } Header section /1996-11-21/Nechako r./ \ HG / 5.771/17:00:02 \ VB / 12.200/17:00:02 \ HG / 5.887/17:10:00 \ HG / 5.669/17:55:00 \ HG / 5.788/18:00:00 \ VB / 12.250/18:00:00 | Data String section HG / 5.657/18:35:00 / HG / 5.797/19:00:00 / VB / 12.280/19:00:00 / HG / 5.718/20:00:00 / VB / 12.280/20:00:00 /

Page 19 of 85

1.A.2 Data Format: GOES Satellite Conventional GOES satellite format SHALL be identical to the following format. FIELD SIZE Platform Id 8 i.e. 45410B6A (hexadecimal) Year 2 i.e. 96 Date/time 9 i.e. 325211519 => Julian day 325 at 21:15:19 Transmission dams 7 i.e. G47-3NN => signal strength and offset frequency Channel 4 i.e. 013E => channel 13 east Others 7 i.e. FF00097 => carrier status (2), message length(5) Sensor code 2 i.e. HG => SHEF code for stage Sample time as required i.e. 15 => 15 minutes prior to transmission Sample interval as required i.e. #60 => sensor value every 60 minutes Sensor value as required i.e. 5.685 => value, up to 7 digits as a minimum, including sign and decimal point (variable position) EXAMPLE GOES FORMAT 45410B6A96325211519G47-3NN013EFF00097:HG 15 #60 5.685 5.718 5.797 :HG 45 #180 5.810 :HG 160 #180 5.657 :VB 15 #60 12.3 12.2 12.2 45410B6A96325181519G46-3NN013EFF00096:HG 15 #60 5.788 5.771 5.858 :HG 65 #180 5.887 :HG 20 #180 5.669 :VB 15 #60 12.3 12.3 12.3 45410B6A96325151519G44-3NN013EFF00097:HG 15 #60 5.832 5.885 0.001 :HG 80 #180 5.917 :HG 185 #180 0.001 :VB 15 #60 12.3 12.2 12.2 HIGH DATA RATE GOES satellite format SHALL be identical to the following format. FIELD SIZE Platform Id 8 i.e. 45410B6A (hexadecimal) Year 2 i.e. 96 Date/time 9 i.e. 325211519 => Julian day 325 at 21:15:19 Transmission dams 7 i.e. G47-3NN => signal strength and offset frequency Channel 4 i.e. 013E => channel 13 east Others 7 i.e. FF00097 => carrier status(2), message length(5) Flag word 1 i.e. X: Flag word 8 bits, refer to High Data Rate version 1.0B specification section 3.1 for more details. Sensor code 2 i.e. HG => SHEF code for stage Sample time as required i.e. 15 => 15 minutes prior to transmission Sample interval as required i.e. #60 => sensor value every 60 minutes Sensor value as required i.e. 5.685 => value, up to 7 digits as a minimum, including sign and decimal point (variable position) EXAMPLE HIGH DATA RATE GOES FORMAT 45410B6A96325211519G47-3NN013EFF00097X :HG 15 #60 5.685 5.718 5.797 :HG 45 #180 5.810 :HG 160 #180 5.657 :VB 15 #60 12.3 12.2 12.2 45410B6A96325181519G46-3NN013EFF00096X :HG 15 #60 5.788 5.771 5.858 :HG 65 #180 5.887 :HG 20 #180 5.669 :VB 15 #60 12.3 12.3 12.3 45410B6A96325151519G44-3NN013EFF00097X :HG 15 #60 5.832 5.885 0.001 :HG 80 #180 5.917 :HG 185 #180 0.001 :VB 15 #60 12.3 12.2 12.2

Page 20 of 85

Appendix 2

Example Performance Specifications for Acoustic Doppler Current Profilers (aDcp)*

* Used with the permission of the Water Survey of Canada, Environment Canada. Document based on 2011 aDcp performance specifications, and may no longer be current.

BACKGROUND: Water Survey of Canada (WSC) a division of Environment Canada (E.C.) is responsible for monitoring over 2000 operational sites and numerous study sites in Canada. WSC collects information on water parameters such as water velocity, water temperature, river cross sectional dimensions etc. performing quality assurance checks in real time and in post processing. Data are required on selected rivers at various spatial and temporal distributions. The spatial needs vary along the river length from headwater stream to estuaries. The temporal needs vary from annual discharge to near instantaneous velocity. Environment Canada’s data are used by several external clients and verification of data quality is critical. These data are archived by Environment Canada in output formats required to mesh with existing systems. The equipment will be used by Water Survey field personnel in carrying out normal water data acquisition duties and in specialized surveys of rivers. The locations of the data collection sites vary from remote locations where access is only available by chartered air transport with limited hauling capacity to road accessed sites. An ideal solution would have the ability to measure the water in a river cross section in most rivers in Canada with minimal estimation of data by extrapolation or interpolation of measured portions. That would include data from the surface to the bed and in the horizontal, across the entire width of the river. The rivers at which measurements are taken vary greatly in environmental conditions, in width, in depth and flow range. They range in size from shallow and narrow creeks which have a very low flow to large, 20+ meter deep rivers as well as rivers that have velocities over 4 meters per second. Many of the rivers may have moving beds or conditions such as aquatic vegetation that make hydroacoustic discharge measurements difficult. Not all rivers may present conditions appropriate to hydroacoustic measurements and as such, the systems adopted must provide means to inform the operator when conditions are either marginal or inadequate for such measurement methods. The Water Survey of Canada requires Acoustic Doppler Current Profilers (aDcp) that measure varying flow velocities and depths. The instrument must adapt to these variations during a continuous transect. An instrument that must be stopped and reconfigured to measure normally expected variations in depths encountered during a transect is not acceptable. The aDcp must have auto adapting functions that will maintain bottom tracking and continue profiling water velocities over a wide range of water depths and velocities during a continuous transect. DEFINITIONS aDcp – Acoustic Doppler Current Profiler GPRMC – NMEA string for minimum Specific GPS – Global Positioning System GPS/transit data RTK – Real-time Kinematic WAAS – Wide area augmentation system NMEA- National Marine Electronics Association DBS – NMEA string for depth below surface SBAS - satellite-based augmentation system DBT – NMEA string for depth below transducer HDOP - horizontal dilution of precision GPZDA – NMEA string for date and time GPVTG - NMEA string for track made good and ground speed GPS GGA – NMEA string for global positioning system fix data [M] – Mandatory elements which must be met

Page 21 of 85

1. ACCURACY & PRECISION - aDcp

1. [M] Must be divided into multiple discrete depth cells

2. [M] Must be reported as 3-d velocity vectors (x,y. z components)

3. [M] Must provide water velocity in reference to true North

4. Velocity determination of sampling volume should be adjusted for pitch and roll

5. [M] Must measure water velocity to an accuracy up to 0.5% of measured water velocity relative to instrument, +/- 5mm/s

1.1 Measure Water velocity:

6. [M] Must measure water velocity through a range of velocities +/-10m/s relative to the instrument. 1. Instrument accuracy for measuring depth should be 1% or better 2. [M] Resolution of depth values must be 2cm or a higher resolution

1.2 Depth

3. Depth determination of individual beams should be corrected for instrument pitch and roll

1. [M] GPS must be either a Novatel GPS or Hemisphere GPS

2. [M] Required correction options include Real Time Kinematic (RTK) and Wide Area Augmentation System. (WAAS)

3. [M] Must support differential global positioning system fix data (GPS GGA) sentences. Must support code 2,4,5 as GPS differentially corrected status code for positions ($GPGGA) for velocity over ground determination. 4. [M] Must support Doppler non-differential GPS for track made good and ground speed ($GPVTG)

5. [M] Must support 3 dimensional (lat, long, elev.) coordinate system

6. Should log satellite vehicle sentences (GPGSV and GPGSA) and recommended Minimum Specific GPS/transit data (GPRMC)

7. [M] RTK GPS accuracy must be sub-meter. (2 sigma)

1.3 GPS

8. Should allow retrieval of RTK base station differential position, (latitude, longitude and elevation). 1. [M] Must integrate data from external GPS onboard the aDcp platform.

2. Should integrate depth below transducer (DBT) and depth below surface (DBS) NMEA strings from external echo sounder.

3. Should integrate data from external heading sensors

4. [M] Heading sensor must have a minimum accuracy of ±2 degrees.

5. [M] Must integrate strings from GPS, operating with outputs at a frequency of at least 5 hertz. Data streams must be merged efficiently and be synchronized to prevent latencies and inaccuracies in resulting data. 6. [M] Must integrate peripherals generating outputs at frequencies slower than the aDcp ping rate.

7. [M] Must allow input of left edge and right edge distances to shore.

8. [M] Must allow manual entry of instrument draft.

9. [M] Must allow user input to screen out effects of flow disturbance near instrument.

10. [M] The system must allow for correction for speed of sound in water.

1.4 Input Capabilities

11. [M] If the correction for speed of sound in water is automatic, the user must be able to override the setting.

Page 22 of 85

1. [M] A higher priority of acquiring and logging data must be given over display of data. Data acquisition must not be delayed as a result of high demand for graphical displays.

1.5 Data acquisition

2. [M] The data must be updated in real time to various views / screens.

1. [M] The user interface must display status of incoming data from peripherals

2. The user interface should indicate when a low supply voltage may impede on data quality

3. The user interface should indicate when instrument not measuring water velocity through full depth of measurable portion cross section.

4. The user interface should indicate when GPS not differential and when the following GPS-related data quality indicators have exceeded a defined limit: horizontal dilution of precision (HDOP), Elevation, differential correction age, constellation change.

5. The user interface should make an audible warning to notify operator of malfunction of the acquisition.

1.6 Onscreen warnings or user prompts during acquisition:

6. The user interface should indicate when instrument is not measuring speed over ground, depth, water velocity.

1. [M] Date

2. [M] Time of day

3. [M] Time elapsed into transect

4. [M] Users must be able to plot the following parameters within graphical cross sectional view and graphical profile view for all velocity reference options (i.e. bottom track, GGA, VTG, instrument).

o water velocity Magnitude Direction individual velocity components (east, north, up) parameter indicating homogeneity of flow at a given

depth(velocity errors or delta velocity) o Signal strength received o An indicator of the quality of velocity measurement (for example

standard deviation of velocity or other scaling indicator)

5. [M] Features within the graphical cross sectional view • Individual cell data values (see specification 1.7.4 for listing of parameters) • Visible measured area boundaries • Identification of data parameter by plot title or legend title • colour coding by magnitude with user configurable legend • Scaling/zoom functions

o Choice of horizontal scale by: • 1) profile number or time; and • 2) distance traveled (length or distance made good)

o User adjustable scaling of parameter magnitude and auto scaling. o User adjustable vertical scale (depth)

6. [M] Graphical profile view (parameter as a function of depth) • User adjustable horizontal and vertical scales • User adjustable colour setting of plotted parameter • Identification of data parameter by plot title or legend title

1.7 [M] Must display the following information for data acquisition and review:

7. [M] Users must be able to view the following parameters within tabular views and plot the following parameters within a graphical time series view. For time series view, users must be able to plot as a function of time elapsed into transect or number of profiles into transect.

• Boat speed

Page 23 of 85

• Heading • Pitch • Roll • Temperature • GPS quality indicator • GPS HDOP • number of GPS satellites • Differential age correction • Water speed

8. Should have average water velocity of measured section to current position.

9. [M] Plan view of boat trajectory with water velocity vectors along the track • Water velocity vectors are to be averaged through the profile • Water velocity vectors should be available by selectable depths

10. [M] Depth displayed in all of the following ways: • tabular • within graphical cross sectional plot • within graphical profile plots

11. [M] The following parameters must be displayed in tabular format • [M] Number of valid velocity cells • [M] Distance made good • [M] Ratio of distance made good and angular differences between bottom

tracking and GPS velocity references. • [M] Distance and azimuth between GPS and bottom track made good

solutions. • [M] Water temperature • [M] GPS data quality indicators • [M] Instruments missing/invalid data • [M] Method used for top, bottom, left and right discharge extrapolation

The following must be displayed within graphical profile plot [M] Profile of measured water velocities to evaluate the quality of top and bottom extrapolations.

12. Loop method correction with option to apply correction to final discharge summary

1.8 Tools for assessing GPS

1. The following are non-mandatory but useful features: • Satellite view showing positions of satellites relative to horizon • Signal strength including floor level and recommended operating signal

strength limit • Ability to display GIS layers as a navigation aid • Ability to reject or add a specific PRN (satellite ID) to optimize GPS fixed

solution computation • Filtering of GPS where speed over ground exceeds a threshold

1. M] There must be quality control mechanisms to detect the effects of the following conditions with a means for the user to assess the effectiveness of these controls:

• [M] Non-homogeneous flow at any given cell. • [M] Very high and very low concentrations of suspended particles.

2. [M] Mitigate impact of disturbances on instrument trajectory. • [M] Corrections must be applied on data to account for instrument heading • [M] Data from internal heading sensor must be assimilated in the

computations at 1 Hz or faster.

3. [M] The user must be provided with a full suite of system diagnostics related to hardware and firmware performance.

4. The system should have automated validation of the speed over ground activated at user choice.

1.9 General data quality features

5. [M] The system must have automated depth validation routine and be activated at user choice.

Page 24 of 85

2. TECHNICAL SPECIFICATIONS - aDcp

2.1 Operating Capabilities

[M] Diagram 1 (see end of document) is a hypothetical river cross section over which an aDcp with the expected auto adapting features must be able to maintain bottom tracking and profile water velocities through the water column across the river.

• Water velocity measurement algorithm must be self adapting to optimize sampling volume and obtain the most accurate water velocity while profiling across the river.

Given the following operating parameters: blanking distance of 20cm; draft typical for an Oceanscience Riverboat deployment;

• The aDcp must measure a minimum of 2 water velocity cells in shallow sections;

• the aDcp must maintain bottom tracking and water velocity tracking between points A and B.

o In favorable water conditions, water velocities must be measured through the deepest section with an extrapolated section near the riverbed no greater than 20% of total depth.

o In unfavorable conditions such as very clear water and high suspended sediment concentrations, the aDcp must also be able to track water velocities to at least 1/3 of the deep section (21/3 = 7m).

1. Should operate from a nominal 12 volt DC source. 2.2 Power Requirements 2. [M] For aDcps supplied with battery packs: Where the ADCP is deployed in a

tethered boat deployment, battery packs must provide operation for a minimum of 4 hours.

1. [M] Equipment must be designed to prevent connection in reverse voltage or be protected against exposure to reverse voltage.

2.3 Voltage Protection

2. Equipment should operate without the need to replace a fuse or open the casing after being subjected to reverse polarity from a 12VDC nominal battery source.

2.4 Electro-magnetic Interference Protection

1. [M] Equipment must not be affected by operation of an adjacent RF modem or a similar electrical device

1. [M] ADCP electronics and transducers without operating batteries and external cables must have a mass equal to or less than 12 Kilograms.

2.5 Physical Properties

2. [M] Non corrosive material must be used for all components exposed to ambient atmospheric humidity and water.

1. [M] Must default to most recent calibration on power up. For example the ADCP must default to last valid beam matrix, compass calibration, electronics calibration upon power up.

2.6 Memory Protection

2. If a power interruption occurs while acquiring data, the user should be warned. 1. [M] Underwater connectors must be water proof.

2. [M] Must have positive locking connectors.

3. [M] Power/Communication cable(s), if applicable, must be at least 5 meters long. If a power cable is required, it must be part of the bid proposal.

4. [M] Cables and connector, if applicable, must remain flexible at -40°C.

5. [M] Performance of cables and connector(s) must not deteriorate through full range of operational air temperatures from -40C to +50°C.

2.7 Cable / Connector Properties

6. All external connectors containing a live wire end should not be susceptible to accidental sparking.

Page 25 of 85

1. [M] Must operate using Serial RS232 standard.

2. Should support baud rates from 9600 to 115200 bps.

3. Communication settings should be programmable (ex. Stop bit, parity, flow control)

4. [M] Must support both RF communication and direct serial communication options for tethered boat and manned boat deployments respectively.

5. [M] RF equipment must be waterproof.

6. [M] RF communications must have a range of at least 400m.

7. [M] Radio modems must be Freewave Technologies modems.

8. [M] Radio modem must be spread spectrum, operating on unlicensed frequencies approved for use within Canada.

2.8 Support of RF and direct Communication. Applies to aDcp and peripherals

9. Should allow option to install external antenna

1. [M] Windows-based software must operate on Microsoft XP, Windows 7 for all modes of operation. 2. [M] Resizeable and movable windows for both data collection, review and instrument configuration must be provided to allow the user to easily adapt the display to show the parameters necessary to acquire and review and verify data quality for various types of data collection.

3. Should feature minimize / restore functions and autoscale features to the maximum and minimum data values for individual window.

4. Where applicable, the individual window should have a user configurable legend.

5. Software should allow short key entry of key software controls.

6. [M] Software must support pointing devices.

7. Font sizes, styles and colours and screen colours should be user selectable to optimize visibility in various outdoor conditions. These settings should be set within application and not applied across all Windows applications.

8. Should have standard windows dialog for file open and save

9. [M] Must allow user to select multiple files to open and process

10. Option to print hardcopy should be available within software for summary reports. i.e. Discharge summary with option to save electronic summary file.

2.9 Windows-based software features

11. [M] Help functions must be available within software.

1. [M] Firmware must be upgradeable without the need to open the electronics housing.

2. Should revert to previous firmware version on upgrade failure. 3. [M] Must report on status of upgrade (success or failure).

4. [M] Must preserve all calibration data during upgrade

2.10 Firmware

5. [M] User must be informed of any change in computations and thus calculated data resulting from the firmware upgrade

1. [M] When the measurement is being recorded within both a PC and aDcp, all site information and aDcp settings must be uploaded to the aDcp.

2. Should allow initialization to manufacture’s default setting

3. [M] Must allow input of station number, station name measurement location and comments with measurement.

2.11 Configuration and file management

4. Set aDcp clock. [M] Must allow clock synchronization to PC time. Should also allow clock synchronization to GPS. Should allow user-configured time zone for aDcp clock output.

Page 26 of 85

5. Help should be available for configuration within the data acquisition software

6. [M] Must save individual configuration per measurement

7. [M] Must support windows file directory structure to store data files

8. System should support user-defined file names that meet Windows file-naming standards. 9. [M] Software must allow users to protect (lock) processed files to prevent inadvertent modification. 1. Should allow recording of the following during acquisition

• External depth sounder raw data • External peripheral for heading

2. [M] Data must be stored on PC or aDcp in real time • If the option of recording in PC and aDcp is available in real time. The

application software should report both date and time of aDcp and computer time.

3. [M] Recording frequency must be at 1 hertz or faster

2.12 Recording

4. [M] User must be able to record diagnostic test and compass calibration results on PC or aDcp.

1. [M] Raw data must not be altered.

2. [M] Must use System International (SI) units. • [M] Final outputs for distance must expressed in meters • [M] Final outputs for area must expressed in square meters • [M] Final outputs for discharge must be expressed in cubic meters per second

3. Averaging data • Users should be able to aggregate the data over user specified number of

profiles or time interval or distance.

4. [M] Users must be able to apply modifications to individual files or multiple files

5. Users should be able to re-compute results for a sub-section of the transect based on a user-selected range of profiles

6. Should offer options to calculate area based on the following: • Perpendicular to the mean flow. • User specified azimuth • Parallel to the average course

7. Must extrapolate into unmeasured portions of the river cross section: • [M] For each transect, extrapolate and display unmeasured discharge for: top,

bottom, left, right • [M] Top and bottom extrapolation methods must include adjustable power law

fit and constant fit. • [M] Left and right bank extrapolation methods must include triangular and

vertical shape factors • [M] Users must be able to specify the number of velocity points that can be

rejected at top and bottom of the profile. • Missing or invalid data within transects should be interpolated and indicated

on displays

8. [M] All data must be referenced spatially and temporally in every transect

2.13 Computation

9. Software should allow re-computation of discharge using a mix of velocity references.

Page 27 of 85

1. [M] The system must produce a discharge summary file. Mandatory discharge summary fields per measurement are listed as follows:

• average total discharge • standard deviation of discharge for selected transects • date of survey • equipment serial number • firmware version • draft of transducer • magnetic declination • software version • References to test files • Identification of survey crew • Station name and station ID • comments

2. [M]. Mandatory discharge summary fields per transect: • transect identification • time of day at start • time elapsed or time of end of measurement • measured, estimated (top, bottom, left, right) and total discharges • mean velocity of boat and water • river width • area

3. [M] Must allow export of discharge summary data files as an ASCII flat file.

4. [M] Must allow export of detailed data for each profile.

2.14 Output

5. [M] Must support all of the following deployment options. • Tethered boat • Manned boat deployment • Mid-section measurement in open water • Mid-section measurement for under ice conditions • Mid-section measurement in combined open water and under ice

conditions

1. [M] Tethered boat must be OceanScience 2. [M] Tethered boat must be a trimaran of durable and rugged (i.e polyethylene) construction. Pontoon (amas) must come apart for portability and allow quick assembly without use of a tool.

3. [M] Non-ferrous materials only must be used within the tethered boat to prevent compass interference.

4. [M] Tethered boat/ADCP assembly must allow mounting of GPS antenna directly above ADCP with 5/8” threaded adapter

2.15 Tethered Boat Platforms

6. [M] Tethered boat must allow water velocity tracking with no significant loss of data in water velocities up to 2.5m/s (refer to WSC SOP for ADCP measurements for allowable % loss of cells)

Page 28 of 85

3. ENVIRONMENTAL SPECIFICATIONS - aDcp

(Referenced Military standard methodology will be used when testing for compliance is required)

1. [M] Operating temperature must be from -5 °Celsius to +40 °Celsius.

2. The warranty should not be voided when instruments is deployed in extreme cold weather (down to potentially -40C). 3. [M] Storage temperature must be from -10 °Celsius to +50 °Celsius.

3.1 Temperature

4. Should withstand instantaneous induced thermal shock of 50°C (example -30°C to+20°C) and operate under thermal shock of 15°C/minute for 2 minutes.

3.2 Vibration 1. [M] Equipment must operate after experiencing a series of mechanical shocks and vibrations similar to what could occur during transportation. Environment Canada reserves to right to test the aDcp to the following standard to confirm if it meets required protection against vibration in transport and operations:

MIL-STD 810F 514.5C-3; restrained; 30 minutes times 3 directions

1. [M] Submerged components must be waterproof to 30m. 3.3 Moisture 2. [M] Internal electronics in submerged compartment must be designed to maintain

operation for a minimum of 2 years without any requirement to return to manufacturer for service or open the sealed electronics compartment for service or maintenance.

Page 29 of 85

Appendix 3

Example of a Qualification Test Procedure for Electronic Data Acquisition System (EDAS) Data Logger*

* Used with the permission of the Water Survey of Canada, Environment Canada.

Document based on 2004 data logger performance specifications, and may no longer be current.

Intended Readership The audience for the Qualification Test Procedures document may include, but is not restricted to: Environment Canada staff responsible for qualification testing of Environmental Data Acquisition Systems (EDAS) as well as current or potential suppliers who wishes to learn about procedures related to qualification testing. Purpose This document provides specific instructions for qualification tests for the DATA LOGGER and its interfaces to external systems. Further requirements for the DATA LOGGER are described in Performance Specifications for EDAS Data Logger in Appendix 1. These tests cover only a limited subset of specifications and it is expected that these tests will expand in scope over the coming years. How to use this Document This document is to be used by Water Survey of Canada personnel responsible for qualifying instrumentation as instructions for DATA LOGGER qualification testing. This document is to be used to conduct tests in a systematic and reasonably efficient manner to confirm products meet most minimal requirements as specified in the performance specifications, and function under conditions expected to be encountered during typical operations. Related Documents [1] Performance Specifications for Environmental Data Acquisition System Data Logger (Appendix 1) [2] MIL standards 810E, MIL STD 461D [3] Other standards. ANSI standard C62.41; NOAA / NESDIS - Certification Standards (2000) [4] SDI-12 Specifications Overview Qualification tests should be based on specifications and be binary Pass/Fail. Testing should simulate both usual and unusual (but realistic) operating conditions. The specifications document provides the basis for this testing and evaluation report. This document relates the functional categories found in the specifications to a series of procedures that can be followed to determine if the product meets the specified requirements. Specifications provide only the minimal requirements and tests have been developed to detect some potential problems that may occur during the course of normal operations. Section 2 duplicates the structure of the performance specifications of the DATA LOGGER data logger with extra space to allow test results, comments and reference to test codes. This can form the basis for the evaluation sheet for the tested product. Each part of the performance specifications in the evaluation template is related to a specific testing procedure through a test code. Some test procedures consist of several sub-steps following a prescribed order so that one test code may apply to several requirements in the specifications. The test code V means do a visual check to confirm the product meets specifications. Test code C means refer to the statement of compliance submitted by the manufacturer. Other test codes are numerical counting up from 3.1, and explained in Section 3.

Section 3 describes the actual test procedures to de carried out. Test procedures must specify how to setup the system to the point where tester inputs may be required, and must then guide the tester through any sequence of actions.

Page 30 of 85

SECTION 2: EVALUATION SHEET

Perf. Spec’n

#

Category Performance Description Pass Test Code Comment

1. Accuracy and Precision Elements

1. The DATA LOGGER shall permit, by means of the PC, the initiation of sensor sampling test cycle and the presentation of these results for analysis.

2. Logger shall also provide diagnostic on its own working integrity.

C

3. Acquisition, archiving routines shall not be interrupted during communications to logger or sensor (via logger) via direct connect PC or telephone communications systems.

3.3

1.1 Data Acquisition Integrity Routines

4. Battery voltage shall be logged in accordance with specification 2.6.Lvl-1.4.

3.2

5. Internal temperature shall be logged in accordance with specification 2.6.Lvl-1.4.

3.2

1. DATA LOGGER logger clock accuracy shall be ±50 ppm per year.

3.8

HDR GOES Option: 2. The logger clock shall be automatically synchronized

to the GOES transmitter clock. C

1.2 Clock Accuracy

3. The HDR 300 and 1200 bps GOES transmitter clock shall comply with NESDIS specifications for HDR GOES sections 3.1, 3.3, 3.4, 3.9.

C

Page 31 of 85


Perf. Spec’n

#


2. Technical Elements

1. Normal operating voltage shall be 11 VDC to 15 VDC. C 2. Shall be protected against voltage levels up to 20

VDC. 3.17

3. Minimum cut-off voltage shall be 10.75 VDC. 3.6 4. Shall be protected for over, under and reverse

voltages 3.17

5. Power consumption, excluding sensors and telemetry hardware, shall not exceed 50 m Amps on average while active and 10 m Amps on average while quiescent for logger only.

C

6. During power interruptions, the DATA LOGGER shall maintain correct time and date references and resume logging when power returns to normal operational levels.

3.3

2.1 Power Requirements

7. Backup batteries shall support easy field replacement - not soldered in place, easily accessible.

V

2.2 Electromagnetic Interference

1. The logger shall not exhibit any malfunction, degradation of performance, or deviation from specified indications when subjected to the radiated electric fields typical of nearby lightning strikes and electrical equipment. (Applicable standard class A3 requirements of MIL-STD-461D for radiated emissions (RE102) and for radiated susceptibility (RS103) or equivalent.).

C

2.3 Surge Protection, Transient Voltage

1. The DATA LOGGER shall withstand repeated power transients resulting from near lightning strikes.

C

Page 32 of 85


Perf. Spec’n

#


2. Equipment shall conform to surge protection standards as detailed in ANSI standard C62.41 “Surge Protection in Low Voltage AC Power Circuits”, Class B

C and Current

3. Equipment shall not be affected by transient voltage and current originating from the power supply or other sources.

C

1. During primary power interruption, memory related to the operating program and data archive shall be protected to maintain correct time and date reference, programmed parameters and data, for a period of not less than 90 days.

3.3

2. Remote access to programming and set-up parameters shall be password protected

3.7

2.4 Memory Protection and EPROM Memory life write expectancy

3. The write / read to EPROM memory shall operate properly for a minimum of 10 years based on measurements at 5 minute intervals and 40 configuration changes per year.

C

1. The firmware that is resident in the DATA LOGGER shall be upgradeable by PC using a method that does not require replacement of DATA LOGGER internal components.

C 2.5 Programming Interface, Firmware and Software

2. All interaction with DATA LOGGER programs including upgrades to DATA LOGGER firmware, data downloads, sensor configurations shall be possible using a PC operating Microsoft Windows XP service pack 2 or Windows 2000

3.2

Page 33 of 85


Perf. Spec’n

#


3. When using a PC, upload and download of parameter set-up sensor management, data acquisition and retrieval shall be accomplished through menus or pop up windows.

3.2

4. Where applicable, input of numeric information shall be in engineering units

5. The DATA LOGGER shall revert to previously stored configuration if abnormal exit from configuration routines occurs.

3.10

Level 1 DATA LOGGER Management of individual sensors:

1. Capability to create, edit or delete specific sensor set-ups.

3.2

2. Data Acquisition a) Start time for data acquisition variable by sensor. b) Acquisition frequency programmable from one

per second to one per day

3.2

3. Data Logging: a) Log data with date and time stamp. b) Logging frequency programmable from 1 per

minute to 1 per day. c) Ability to turn log on and off.

3.2

4. Maximum and/or minimum sensed values: a) Determine values, programmable from 1 per

second to 1 per day; b) Log value with date and time stamp of actual

acquisition time (to the nearest second) of the occurrence of max and/or min.

3.2

2.6 Sensor Management and Output Management

5. Alphanumeric sensor labeling (2 characters minimum length).

3.2

Page 34 of 85


Perf. Spec’n

#


6. Individual sensors are independently programmable. 3.2

7. Position of decimal point variable by sensor for any position.

3.2

8. Activation of a sensor (on/off designation).

3.2

9. Data download from user selectable date.

3.2

10. Provide for logging on PC or DATA LOGGER continuous live readings for user selectable sensors with date, time stamp, and labels.

3.2

11. Data output shall be selectable by parameter

3.2

12. Direct access (transparent mode) to SDI-12 bus.

3.2

13. Capability of logging a minimum of 10 distinct parameters

14. Mathematical functions: Z = F; Z = X; add; subtract; multiply; divide; Min; max; average; Slope & Offset; >,<, User defined equation.

C, 3.2

15. Telemetry data output for transmission shall be selectable by interval (i.e. with data collected at 15 minute intervals, only hourly values can be transmitted; data logged prior to the transmission interval can be sent as redundant data).

3.11

16. Ability to run the logger in standard time with an option to offset for Coordinated Universal Time (UTC).

3.11

Page 35 of 85


Perf. Spec’n

#


17. Ability to acquire sensed data in time ordered, event ordered and gradient intervals.

C

18. Level 2 DATA LOGGER as above plus shall have the following features as minimum.

19. The following range of math instructions: sqrt; ln(X); eX ; xy ; π (Pi ) ; abs; frac; int; mod; sine; cosine; tangent; inverse (sine, cosine tangent); block move; sliding block move; spatial max; spatial min; spatial average; vector averaging; minimum 5th order polynomials; mathematical functions are executed using the normal mathematical precedence. A minimum of 10 user defined equations of up to 120 characters per equation.

C 3.14

20. Logging frequency programmable from 1 per second to 1 per day.

C

21. Programmable alarm function (gradient and level). Shall also have the capability of triggering a function (e.g. reading another sensor)

C

22. Logger shall have a sensor warm-up function. C

23. Capability of logging a minimum of 15 distinct parameters.

C

Page 36 of 85


Perf. Spec’n

#


1. The DATA LOGGER shall have a minimum of 200 days data storage for three (3) environmental parameters logged hourly, with one maximum and one minimum per day, based on 5 minute samples of the sensor; maintenance parameters logged once per day; all previous complete with date and time stamp and data labels.

3.12

2. There shall be a warning about potential memory erasure/data loss if user actions could result in such an occurrence.

3.12

2.7

Data Storage

3. Shall provide first in-first out memory overwrite

C

2.8 Data Handling 1. Logger shall accept and store data that may have up to 7 significant digits, with the position of the decimal point variable by sensor for any position.

2. Data download: 1. The data that is resident in the DATA LOGGER

shall be downloadable by direct connect to a PC. 2. For data logged as per Data Storage item 2.7.1

the elapsed time of download shall not exceed ten minutes from start of download to resultant ASCII file stored on PC.

3. The resultant output shall be in tabular or sequential ASCII format as described in Appendix 1.A.1.

4. The output shall allow up to 7 digits as a minimum, not including decimal point and sign, with the position of the decimal point variable by sensor.

3.2 3.2 3.12

Page 37 of 85


Perf. Spec’n

#


3. For Level 1 DATA LOGGER, all intermediate calculations shall provide results equivalent to 32-bit long integer architecture as a minimum.

C

4. For Level 2 DATA LOGGER, all intermediate calculations shall provide results equivalent to 32-bit IEEE 4-byte Real (Single Precision, Floating Point) as a minimum.

C

5. HDR GOES Option: 6. GOES satellite data (conventional data rate and high

data rate) shall be in ASCII format as described in Appendix 1.A.2.

7. When transmitter is configured to transmit at conventional data rates, data transmitted via GOES satellite shall be centered in the assigned transmission window.

3.11 C

2.9 Telecommunications 1. DATA LOGGER firmware shall support modem and

HDR GOES satellite telecommunications. C

2. Telecommunications capability shall be available as options to the logger, to be ordered as required.

C

Modem Communications shall be:

3. supported via supplier modems or third party modems; 4. via modems programmable up to at least 9600 baud. C DATA LOGGER with HDR GOES satellite communications:

5. DATA LOGGER and transmitter (High Data Rate) shall meet all criteria for HDR GOES (NOAA/NESDIS March 2000).

C

Page 38 of 85


Perf. Spec’n

#


6. DATA LOGGER shall operate in random as well as self-timed transmission modes;

C

7. DATA LOGGER shall show continually updated timing status on request, including present time, time to next data acquisition and time to next transmission.

3.11

8. The HDR GOES output message length shall be truncated by the DATA LOGGER to prevent trip of the fail safe (as per NESDIS High Data Rate specification).

C

9. Satellite transmitting antenna shall be to NESDIS specifications.

C

10. Satellite transmitting antenna beam width shall be wide enough to include a pair of GOES satellites and shall deliver the maximum possible power to reach both satellites.

C

11. Satellite transmitting antenna shall come with mounting hardware.

C

2.10 Input / Output

Ports Level 1 DATA LOGGER shall have: 1. RS232: 1 serial port; used for DATA LOGGER and

sensor configuration and data retrieval via direct connect PC or external data communications device, baud rate programmable up to at least 9600, compliant with RS232 standards.

V 3.2

2. If the GOES option is ordered, connection and operation of external transmitters shall not interfere with use of the RS232 port as defined in 2.10.Lvl-1.

3.11

3. SDI-12: 1 port (3 wire), minimum full SDI-12 3.1

Page 39 of 85


Perf. Spec’n

#


capability using the latest (downward compatible) published version.

Level 2 DATA LOGGER: as above plus shall have: 4. RS232: a second serial port identical to the above,

with both ports individually programmable (Note: If only one RS232 port is provided, the supplier shall demonstrate how that one port can provide the same functionality, including that of element 1.1.2, that two separate ports would provide);

V 3.15

5. Event: 1 port, minimum 16 bit counter, 20ms closure, rollover or reset software selectable.

V, C

6. Analog: 2 differential configurable to 4 single ended; resolution 1 bit or 0.025% full scale; analog to digital conversion minimum 12 bits (plus one sign bit); range ±5 volts DC and accuracy 0.1% full scale, temperature compensated over full range of operating temperatures. (Note: if voltage range input is less than ±5 volts, supplier shall demonstrate how the above accuracy can be achieved).

V,C

7. Excitation: 2 ports, switched under software control, programmable from 0 to 5 V at 1% full scale resolution, accuracy at 0.1% full scale, range 0 to 5 volts DC, load compensated up to 20 m Amps (Note: if voltage range output is less than 5 volts, supplier shall demonstrate how the above accuracy can be achieved).

V 3.16

Page 40 of 85


Perf. Spec’n

#


8. Switched: one 12 VDC power output port to be used for sensor activation that shall be enabled and disabled by software and shall have an output current of at least 500 m Amps.

V 3.17

1. All connectors used for operation, maintenance, communication and sensor connection shall be clearly labeled.

V

2. All connectors shall be equipped with a positive locking mechanism that will prevent inadvertent separation of the plug and socket.

V

3. All connectors containing a live wire end with the exception of the telephone RJ-11 shall be female.

V

4. Sensor connection to the DATA LOGGER shall be by terminal strip or individual connectors or a combination thereof.

V

2.11 Connectors

5. Insulation displacement connectors shall conform to the requirements of MIL-C-83503A or equivalent.

V

1. A minimum 2.5 meter long power cable with appropriate connectors shall be supplied.

V

2. A minimum 2.0 meter long communication cable shall be provided complete with a DB9 female connector on the computer end and an appropriate connector on the logger end.

V

DATA LOGGER with Modem Communications

2.12 Cables

3. If an external modem is supplied, a minimum 1.5 meter long communication cable between the modem and DATA LOGGER shall be provided, complete with the appropriate environmental connectors.

V

Page 41 of 85


Perf. Spec’n

#


DATA LOGGER with HDR GOES Transmitter / Telemetry

4. If satellite antenna is supplied, a minimum 4.5 meter antenna cable shall be supplied, complete with the appropriate environmental connectors.

V

5. If HDR GOES transmitter and GPS antenna are supplied, a minimum 4.5 meter GPS antenna cable shall be supplied, complete with the appropriate environmental connectors.

V

2.13 Dimensions 1. The DATA LOGGER shall not exceed volume defined by a 40cm X 40cm X 40 cm box.

V

3. Environmental Elements

1. Equipment shall operate through an ambient temperature range of -40oC to +50oC.

C

2. Equipment shall withstand temperatures from -60oC to +65oC

C

3.1 Operating Temperatures

3. When equipment is exposed to temperatures beyond the operating range specified in 3.1.1, equipment shall automatically recommence normal operation when operating temperatures are achieved.

C

Page 42 of 85


Perf. Spec’n

#


4. Cables shall remain flexible at -40oC (shall maintain insulation properties and not become brittle)

C

5. Cables shall not deteriorate at +65oC. (shall maintain insulation properties)

C

1. Equipment shall operate under humidity conditions similar to what may occur within an unventilated shelter located above a well during a hot summer spell, equivalent to cyclic variations in humidity experienced over a period of 10 days with a relative humidity ranging from 74% to no less than 95%, condensing as the temperature ranges from +26˚C to +35˚C.

C 3.2 Relative Humidity and Moisture

2. Casing shall be water resistant. C 1. Equipment shall operate under thermal shock of

15oC/min. for 2 minutes (-20oC to +10oC). C 3.3 Thermal Shock

2. Equipment shall withstand instantaneous induced thermal shock during transport of 70oC (-50oC to +20oC)

C

Mechanical Shock 3. Equipment shall operate after experiencing a series of mechanical shocks equivalent to 18 impact shocks of 15g consisting of 3 shocks in each direction (6 in total) applied to each of 3 mutually perpendicular axes of the equipment.

C

3.4 Vibration 1. Equipment shall withstand vibrations similar to what occurs during transportation, equivalent to non-uniform harmonic vibrations with frequencies ranging from 10Hz to 50 Hz and accelerations of up to 2 G taking place over periods of 2 hours along each of the 3 mutually perpendicular axes of the equipment.

C

Page 43 of 85


Perf. Spec’n

#


3.5 Solar Radiation* 1. Components shall withstand repeated exposure to solar radiation of 1022 W/m2

C

3.6 Wind* 1. Components shall withstand average hourly wind speed of 160 km/h. (*Outdoor mounted components only)

C

3.7 Sand & Dust 1. Sand and dust shall not alter the operation of equipment.

C

3.8 .Ice Accretion* 1. Components shall operate under icing conditions of 50mm thickness and specific gravity of 0.9.

C

3.9 Corrosion Protection

1. Corrosion resistant materials shall be used C

pg. 44 of 85

SECTION 3: Test Descriptions And Pass Criteria – Data Logger Hands-on test procedures: Before test: Supplier shall provide the configuration setup file to upload to DATA LOGGER (or preloaded) to conduct test. Suppliers to ensure that loggers are configured as follows: Sensor SDI address = 0 Measurement type = M0 Label: HG Slope: 1 Offset: 0 Number of decimal place after the point 3 decimal. SDI-12 sensor acquisition frequency every minute (00:01:00) synchronized to top of hour Max min average interval set to 5 min (00:05:00) synchronized from top of hour to fifth value. (i.e 00:00:00 to 00:04:00) Tester to set: the Sensor Initial setting = 10.000m (sensor will be a shaft encoder with digital display) Instruction to port over direct SDI command shall be provided. Internal temperature (to one decimal place) and externally supplied voltage (to two decimal places) to be logged at one minute intervals. All sensors will be tested with SDI-12 verifier by testing group to ensure they are compatible with most recent version of SDI-12. Power will be supplied to shaft encoder directly from battery or source. Testers are to keep a notebook. On test result sheets, record name of tester, product make/model, serial number, test number, time of start and end of test, note results. For each test use the site description field within logger to record the test location and test number. Save all log files to individual CD’s for each product. Name each log file according to date, six letter ID for product and test number. Format:TESTID_ProductName_YYYYMMDD HHMM.txt Example: for test 3.1 (test SDI compatibility) for product “exampl” - 31_Exampl_1_20050115_1125.txt The configuration file naming convention. TESID_ProductName_YYYYMMDD_HHMM.ext If information is binary, a readable ascii version shall be provided with explanation.

Test setup for acceptance tests 3.2 to 3.5

Testers will be monitoring the SDI bus by connecting the second com port on the PC set at 1200E71. Pin 2 is connected to the data line and pin 5 connected to the ground.

pg. 45 of 85

Test 3.1

Objectives: Confirm SDI-12 version is latest available version, check SDI commands and timing. Procedures to be followed by testers. Use NR Systems’ SDI-12 Verifier to check SDI-12 commands and timing. Ensure that the appropriate version of SDI-12 Verifier is used to confirm compliance to specification. Passing criteria: DATA LOGGER must be substantially compliant to Version 1.3 of SDI-12 (or most current version as of date of test). Should some commands be found non-compliant, a successful supplier will be allowed one month to achieve full compliancy after Supplier has received written notice. Before each test from 3.2 to 3.5, delete previously logged data. If DATA LOGGER allows both sequential and tabular formats, only a pass in one of two formats is required but tests are to be done in both formats to detect potential problems.

Test 3.2

Objectives: Test end of year date rollover. Test min, max and average functions. Procedures to be followed by testers. 1. Set date to 2005-12-31 23:53:00. For roll-over tests on GOES-enabled DATA LOGGER units where date can be modified, use the offset for Coordinated Universal Time to work around automatic clock synchronization. If date cannot be modified, rollover test is not necessary. For GOES enabled DATA LOGGER units, transmit data over one or two transmissions and retrieve to confirm format is consistent with DATA LOGGER performance specifications and transmitted data matches logged data. start acquisition Shaft encoder SDI assigned address is zero. * Uncertainty in expected value reflects reasonable errors in operating a shaft encoder with digital display by hand. Allowances may be made for values generated outside this error. Errors generated do not automatically indicate failure for DATA LOGGER. A test with non-compliant result(s) would be repeated using a different sensor, make and model.

Time hh:mm:ss

Procedure Expected Value (m)

+/- .002m*

Passing criteria

23:55:00 Note timing and value transmitted to logger each

minute

10.000

23:56:00 10.000 23:57:00 10.000 23:58:00 10.000 23:59:00 10.000 Average, min and max for 5 minute

interval = 10.000m (+/- 0.002m). Time stamps for min and max shall be at first

occurrence throughout tests. Output data format shall match one of two options shown in specifications for

Data Logger, Appendix 1. 00:00:00 10.000 00:01:00 10.000 00:01:20

to 00:01:40

Turn shaft encoder wheel while observing digital

display

00:02:00 10.100 00:02:20

to 00:02:40


display

00:03:00 10.200 00:03:20

to 00:03:40


display

pg. 46 of 85

00:04:00 10.300 Average, min and max for 5 minute interval = 10.120, 10.000 and 10.300m

(+/- 0.002m)respectively Clock and date, archived data, time

stamps to continue as indicated after rollover. Internal voltage and temp with time stamps to continue after rollover.

00:05:00 10.400 00:06:00 10.400 00:06:20

to 00:06:40


display

00:07:00 10.5 00:07:20

to 00:07:40


display

00:08:00 10.2 00:08:20

to 00:08:40


display


(+/-0.002m) respectively 00:10:00 10.000 00:11:00 10.000 00:11:20

to 00:11:40


display

00:12:00 11.200 00:12:20

to 00:12:40


display

00:13:00 8.500 00:13:20

to 00:13:40


display


(+/-0.002m) respectively 00:14:20

to 00:14:40


display

00:15:00 end test

9.000

pg. 47 of 85

Test 3.3

Objectives: Test leap year rollover scenario #1. Test primary power interruption to DATA LOGGER, power interruption to sensor, test SDI communication error. These tests are intended to detect integrity of logged and archived data and metadata as well as blunders in calculating mins, maxs and averages when primary power to either the sensor or DATA LOGGER is interrupted or if SDI-12 communications is interrupted. These interruptions may occur at the beginning, end or middle of an averaging interval so these scenarios will be tested. Testers will ensure that backup battery on the shaft encoder is in good working order. Procedures to be followed by testers. 1. Set date to 2005-2-28 23:53:00 (leap year scenario #1 is end of February in non-leap year) and synchronize watches with the logger clock. Once logger has been powered down and back up, the watch will be the means of tracking timing of actions. start acquisition

Time Procedure Expected Value (m) +/- .002m*

Passing criteria


minute

10.000

23:56:00 10.000 23:56:20

to 23:56:40

Turn shaft encoder wheel while observing digital display

23:57:00 10.300 23:57:20

to 23:57:40


23:58:00 9.600 23:58:30 Shut off primary power to

DATA LOGGER

23:59:00

00:00:00 00:01:00 00:01:30 Turn on primary power to

DATA LOGGER. After powering back up, do not

activate menu on logger with PC. Test is intended to

simulate power down and reacquisition without external

assistance.

.

00:02:00 9.600 00:03:00 9.600

pg. 48 of 85

00:04:00 9.600 Average, min and max for 5 minute interval = missing or no values or 9.600 (+/-

0.002m). Missing data format as specified in appendix 1.A in the performance

specifications for DATA LOGGER. Clock and date, archived data, time stamps to continue as indicated after rollover and power up. Some time allowance will be

made for reacquisition. Internal voltage and temp with time stamps continued after

rollover. No spurious values for temperature or voltage after re-

establishment of power. 00:05:00 9.600 00:06:00 9.600 00:6:20

to 00:06:40


00:07:00 10.000 00:07:30 Disconnect SDI

communications between DATA LOGGER and sensor

00:08:00 00:08:30 Reconnect SDI


00:09:00 10.000 Average, min and max for 5 minute interval = missing value or 9.80, 9.600 10.000 (+/-

0.002m). Missing data format to be as specified in appendix 1.A in the

performance specifications for DATA LOGGER.

00:10:00 10.000 00:11:00 10.000 00:11:20

to 00:11:40


00:12:00 9.900 00:12:20

to 00:12:40


00:13:00 00:13:30 Disconnect SDI


00:14:00 9.800 Average, min and max for 5 minute interval = missing value or 9.925, 9.800, 10.000

(+/- 0.002m). Missing data format to be as specified in appendix 1.A in the

performance specifications for DATA LOGGER. Time stamps to continue after communication interruption. No spurious

values for temperature or voltage. 00:14:30 Reconnect SDI


pg. 49 of 85

00:15:00 9.800

00:15:20 to

00:15:40


00:16:00 9.700 00:17:00 9.700 00:17:20

to 00:17:40


00:18:00 9.900 00:19:00 9.900 Average, min and max for 5 minute interval

9.8, 9.700 9.900 (+/- 0.002m) 00:20:00 End test

9.900

Timestamps(HH:MM:SS), dates, sensor codes(up to eight characters), values up to seven significant figures with variable decimal point positions, comma or slash delimiters, missing data flags are the essential elements in an output file. If the format varies from specifications, the primary bidder will be given 4 weeks to conform to WSC output format or a variation deemed acceptable by WSC. Failure to conform within that period of time will result in award to secondary qualified bidder.

pg. 50 of 85

Test 3.4

Objectives: Test leap year rollover scenario #2. 1. Set date to 2008-2-28 23:57:00 (second last day in February in leap year) Start acquisition.

Time Procedure Expected Value (m) +/- .002m*

Passing criteria


minute

10.000

23:54:00 10.000 23:54:20

to 23:54:40


23:55:00 10.100 23:56:00 10.100 23:56:20

to 23:56:40


23:57:00 10.200 23:57:20

to 23:57:40



= 10.240, 10.100 and 10.400m (+/-0.002m) respectively

00:00:00 10.400 00:01:00 10.400 00:02:00 10.400 00:02:20

to 00:02:40



= 10.320, 10.200 and 10.400m (+/-0.002m) respectively

00:05:00 10.200

Test 3.5 Objectives: Test leap year rollover scenario #3. 1. Set date to 2008-2-29 23:57:00 (last day in February in leap year) Start acquisition. Repeat procedure as in test 3.4. 1. Note rollover and observe date, time, archived data and timestamps, internal voltage and

temperature values and timestamps. Passing criteria: Time, archived data and timestamps, internal voltage and temperature values and timestamps are continuous and do not exhibit any jumps or spurious values.

pg. 51 of 85

Test 3.6 Objective: Test for minimum cut-off voltage: Required equipment: Connect calibrated programmable DC power supply. Program power supply to power logger with a voltage of 11.5 VDC gradually reducing by 0.1V increments every minute to 10VDC. Note voltage at which logger powers down. Passing criteria: Cut-off voltage between 11.0 and 10.7 VDC is acceptable.

Test 3.7 Objective: Test for password protection Set up password protection and attempt to enter using another arbitrarily selected code. Attempt modem access while direct communications is established noting if modem access is granted without a password. Disconnect communications cable. Reconnect 5 minutes later noting if password is required to change configuration. Passing Criteria: DATA LOGGER must have option to set up password and shall not allow access to data or changes to configuration setting without use of the password(s). Once password access has been granted, access by other users through a modem shall not be possible without password. Disconnection and subsequent reconnection of direct communications cable 5 minutes afterward shall require password to access DATA LOGGER settings.

Test 3.8 Objective: Test for DATA LOGGER clock accuracy Overnight test. Set clock by synchronizing with NRCan’s audio time signal (+/- 1 second).Twenty-four hours later, confirm clock is within 5 seconds of NRCan time signal Passing criteria: Shall be within 5 seconds of second time signal

Test 3.9 Objective: Test for method of installing firmware upgrade Confirm method of installing firmware upgrades does not require replacement of DATA LOGGER internal components. Passing criteria: In order to upgrade firmware, use of a PCMCIA card is acceptable but replacement of a component that is not designed to be regularly transported and handled external to the DATA LOGGER is not acceptable.

Test 3.10 Objective: Test for abnormal exit from configuration routine. Shut down primary power to the DATA LOGGER while configuring one sensor. Reinstate power and confirm that original configuration is maintained. Passing criteria: DATA LOGGER shall maintain acquisition interval, SDI address and any offset and gradient information that was saved prior to the reconfiguration exercise.

pg. 52 of 85

Test 3.11 Objective: Tests for DATA LOGGER with GOES option Supplier shall provide the configuration setup file to upload to DATA LOGGER (or preloaded) to conduct test. Suppliers to ensure that loggers are configured as follows: Sensor #1 – Simulated water level HG Sensor SDI address = 0 Measurement type = M0 Label: HG Slope: 1 Offset: 0 Number of decimal place after the point 3 decimals. Transmission settings: channel 195, (PDT and time slot to be issued), Tx window length 15 seconds, period of transmission every 30 minutes and baud rate 300. SDI-12 sensor acquisition frequency every five minutes (00:05:00) synchronized to top of hour Max, min interval set to 1/2 hour (00:30:00) synchronized from top of hour to sixth value. (i.e 00:00:00 to 00:25:00) DATA LOGGER will be configured to transmit data for HG at ½ hour intervals, sending redundant data from previous ½ hour. Sensor #2 - Battery voltage Label: VB Set to acquire and log every 10 minutes sending only a single value on the half hour. A PC operating Windows XP service pack 2 will be connected through the RS-232 port logging real-time data while the DATA LOGGER is logging and transmitting. During transmission there should be no interference to the transmission when the PC is connected to the DATA LOGGER. Once an initial transmission has been sent, the PC may be disconnected for the remainder of the test. Confirm that DATA LOGGER can display continually updated timing status on request, including present time, time to next data acquisition and time to next transmission. Run for 24 hours. Check transmitted data against logged data. Power interruption test Cut power to DATA LOGGER for 15 seconds 20 minutes prior to transmission. Re-establish power, let it reboot, acquire data and transmit. Simulation of power supply problem to transmitter This portion of the test is intended to confirm that the logger will not stop functioning if the transmitter ceases to function. 15 minutes prior to transmission, disconnect power to transmitter maintaining power to logger, reconnect 5 minutes after transmission. Confirm logger acquires and logs data during and after communications cable is reconnected. This test is not required in integrated logger-transmitters that do not have an easily accessed power link between logger and GOES transmitter. Pass Criteria: During transmission there should be no interference to the transmission when the PC is connected to the DATA LOGGER. The DATA LOGGER shall be able to send redundant data. After power interruption, all sensor acquisition, logging and transmission settings are to be maintained and transmitted data and timestamps shall not have any spurious values. Confirm logger acquires and logs data during and after transmitter power is reconnected.

pg. 53 of 85

Test 3.12 Objective: Test memory capacity, warnings related to data loss and output: A test for this spec requires a minimum of 16000 data points in the memory. Level 1 loggers are required to log only once per minute. If the logger can log once per second (as stated in specifications for level 2) then we can acquire data from a single sensor for 5 hours or less to acquire 16000 data points. For level 1 loggers it may be possible to fill memory by logging one sensor once per minute as per specifications and assigning up to 10 logged values from each reading. When starting logging, note time and initial value(s) for each parameter. When more than 16000 points have been logged. Configure SDI-12 compatible submersible pressure transducer to acquire and log once per minute with an integration time of ten seconds. Download the archive. Do not delete any data. Note time to download. Stop acquisition and note time when stopped. Look at downloaded data to confirm data integrity. Plot time series of data to confirm data does not contain outliers. Delete entire memory. Confirm warning appears before proceeding. Pass criteria: Download time for 16000 data points with timestamps to a PC shall not exceed 10 minutes. Downloaded output in ASCII format shall be in the same format as shown in Appendix 1.A, DATA LOGGER specification document Before archived data points are to be erased, or overwritten, a warning message must be displayed to the user.

Level 2 DATA LOGGER only

Test 3.13

Objective: Test HDR-DATA LOGGER clock synchronization Set DATA LOGGER clock to two minutes ahead of actual time, simulating case where DATA LOGGER clock has drifted in storage. Configure sensors for data acquisition to same as specified in test 3.2. Start acquisition. Program HDR to transmit at 100 baud, hourly, for 24 hours. Passing criteria: DATA LOGGER shall transmit all instantaneous, min,max and average data with timestamps. Timestamps shall be updated after first transmission.

Test 3.14 Objective: Test mathematical function Program predefined equation T = (C5x

5+C4x4 + C3x3 + C2x2 + C1x + C) to test for 5th order polynomial

calculation. Passing criteria: DATA LOGGER shall be able to accept 5th order polynomial equation. Answer shall be equal to that calculated using a PC with 32 bit architecture to 4 significant figures.

Test 3.15 Objective: Test Excitation port: Confirm presence of 2 ports. Confirm that the menu allows software control to enable and disable excitation port. Passing criteria: DATA LOGGER shall allow individual ports to be enabled and disabled via menu and programmable with respect to voltage levels from at least 0 to 5 volts.

Test 3.16 Objective: Test 12 VDC switched output: Using the menu, through the utility enable and disable the switched output. Putting the output through a typical load, use a precision meter to measure output. Passing Criteria: Output current shall be at least 500mA.

pg. 54 of 85

Test 3.17 Objective: Test DATA LOGGER against over and reverse voltages. Using a precision DC power supply, raise input voltage to 19.5VDC for less than 5 seconds. Reduce the voltage levels. Using a precision DC power supply, set at 12VDC, reverse polarity and turn on power to DATA LOGGER for no more than 3 seconds. Configure an SDI-12 sensor, acquire and log data, as in test 3.2. Transmit through the GOES (if applicable). Passing criteria: All logged and transmitted data contain no spurious values. There is no loss of menu functionality.

pg. 55 of 85

Appendix 4

List of References Related to Use of Hydroacoustic Technologies in Moving-Boat Flow Measurements

as posted on the USGS OSW Hydroacoustics Website (http://hydroacoustics.usgs.gov/movingboat/mbd_references.shtml)

USGS Publications Measuring Discharge with Acoustic Doppler Current Profilers from a Moving Boat by David S. Mueller and Chad R. Wagner. Published as U.S. Geological Survey Techniques and Methods 3A-22, 2009. Acoustic Doppler Current Profiler Applications Used in Rivers and Estuaries by the U.S. Geological Survey by A.J. Gotvald and K.A. Oberg. Published as U.S. Geological Survey Fact Sheet 2008-3096 Quality-Assurance Plan for Discharge Measurements Using Acoustic Doppler Current Profilers by Kevin A. Oberg, Scott E. Morlock, and William S. Caldwell. Published as U.S. Geological Survey Scientific Investigations Report 2005-5183. Summary of 2007 California District ADCP Check Measurements, Sacramento River at Colusa, CA by California Water Science Center (WSC). An internal report summarizing comparison of ADCP check measurements made by California WSC and other agencies. Application of the Loop Method for Correcting Acoustic Doppler Current Profiler Discharge Measurements Biased by Sediment Transport By David S. Mueller and Chad R. Wagner. Published as U.S. Geological Survey Scientific Investigations Report 2006-5079. Tethered Acoustic Doppler Current Profiler Platforms for Measuring Streamflow by Michael S. Rehmel, James A. Stewart, and Scott E. Morlock. Published as U.S. Geological Survey Open-File Report 03-237, 2003. Evaluation of Acoustic Doppler Current Profiler Measurements of River Discharge by Scott E. Morlock. Published as U.S. Geological Survey Water-Resources Investigations Report 95-4218, 1996. Discharge Measurements using a Broad-band Acoustic Doppler Current Profiler by Michael Simpson. Published as U.S. Geological Survey Open-File Report 01-01, 2002. Calibration and Validation of a Two-Dimensional Hydrodynamic Model of the Ohio River, Jefferson County, Kentucky by Chad R. Wagner and David S. Mueller. Published as U.S. Geological Survey Water-Resources Investigations Report 01-4091. Results of a Two-Dimensional Hydrodynamic and Sediment-Transport Model to Predict the Effects of the Phased Construction and Operation of the Olmsted Locks and Dam on the Ohio River near Olmsted, Illinois by Chad R. Wagner. Published as U.S. Geological Survey Water-Resources Investigations Report 03-4336. Journal Articles Special Edition of Journal of Hydraulic Engineering The following papers were published by the American Society of Civil Engineers in a Special Edition of the Journal of Hydraulic Engineering (December 2007) on hydroacoustic research and applications. This publication includes eight papers with USGS authors (see table of contents below). USGS authored papers are available in pdf by clicking on the titles below. Individual papers from non-USGS authors can be purchased at ASCE's Online Library. Editorial Acoustic Velocimetry for Riverine Environments Marian Muste, Tracy Vermeyen, Rollin Hotchkiss, and Kevin Oberg

pg. 56 of 85

Technical Papers Evaluation of Mean Velocity and Turbulence Measurements with ADCPs Elizabeth A. Nystrom, Chris R. Rehmann, and Kevin A. Oberg Field Assessment of Alternative Bed-Load Transport Estimators D. Gaeuman and R. B. Jacobson Correcting Acoustic Doppler Current Profiler Discharge Measurements Biased by Sediment Transport David S. Mueller and Chad R. Wagner ADCP Measurements of Gravity Currents in the Chicago River, Illinois Carlos M. Garcia, Kevin Oberg, and Marcelo H. Garcia Errors in Acoustic Doppler Profiler Velocity Measurements Caused by Flow Disturbance David S. Mueller, Jorge D. Abad, Carlos M. Garcia, Jeffery W Gartner, Marcelo H. Garcia, and Kevin A. Oberg Validation of Streamflow Measurements Made with Acoustic Doppler Current Profilers Kevin Oberg and David S. Mueller Other Journal Articles Comparison of bottom-track to global positioning system referenced discharges measured using an acoustic Doppler current profiler by Chad Wagner and David Mueller. Published in Journal of Hydrology, 2011. Measuring real-time streamflow using emerging technologies: Radar, hydroacoustics, and the probability concept by John Fulton and Joseph Ostrowski. Published in Journal of Hydrology, 2008. Correcting acoustic Doppler current profiler discharge measurement bias from moving-bed conditions without global positioning during the 2004 Glen Canyon Dam controlled flood on the Colorado River by Jeffrey W. Gartner and Neil K. Ganju. Published in Limnology and Oceanography: Methods, 2007. Flow over Bedforms in a Large Sand-Bed River: A Field Investigation by R.R. Holmes, Jr., and M.H. Garcia. Published in Journal of Hydraulic Research, 2007. Repeated surveys by acoustic Doppler current profiler for flow and sediment dynamics in a tidal river by R.L. Dinehart, J.R. Burau. Published in Journal of Hydrology, 2005. Averaged indicators of secondary flow in repeated acoustic Doppler current profiler crossings of bends by R.L. Dinehart, J.R. Burau. Published in Water Resources Research, Vol. 41, 2005. Conference Papers Temporal Characteristics of Coherent Flow Structures generated over Alluvial Sand Dunes, Mississippi River, revealed by Acoustic Doppler Current Profiling and Multibeam Echo Sounding by J. A. Czuba K.A. Oberg, J.L. Best, D.R. Parsons, S.M. Simmons, K.K. Johnson, and C. Malzone. Presented at River Coastal Estuarine Morphodynamics 2009, September 2009. Velocity Mapping in the Lower Congo River: A First Look at the Unique Bathymetry and Hydrodynamics of Bulu Reach, West Central Africa by P.R. Jackson, K.A. Oberg, N. Gardiner, and J. Shelton. Presented at River Coastal Estuarine Morphodynamics 2009, September 2009. Discharge and Other Hydraulic Measurements for Characterizing the Hydraulics of Lower Congo River, July 2008 by Kevin Oberg, John M. Shelton, Ned Gardiner, and P. Ryan Jackson. Presented at 33rd IAHR Congress, August 2009. The Effect of Channel Shape, Bed Morphology, and Shipwrecks on Flow Velocities in the Upper St. Clair River by Kevin Oberg, John M. Shelton, Ned Gardiner, and P. Ryan Jackson. Presented at 33rd IAHR Congress, August 2009. Validation of Exposure Time for Discharge Measurements made with Two Bottom-Tracking Acoustic Doppler Current Profilers by Jonathan A. Czuba, Kevin Oberg, Jim Best, and Daniel R. Parsons. Presented at IEEE Current Measurement Technology Conference, March 2008. Measuring Gravity Currents in the Chicago River, Chicago, Illinois by Kevin A. Oberg, Jonathan A. Czuba, and Kevin K. Johnson. Presented at IEEE Current Measurement Technology Conference, March 2008. Analysis of Exposure Time on Streamflow Measurements Made with Acoustic Doppler Current Profilers by Kevin A. Oberg and David S. Mueller. Presented at Hydraulic Measurements and Experiemental Methods 2007, September 2007. Field Evaluation Of Boat-Mounted Acoustic Doppler Instruments Used To Measure Streamflow by David S. Mueller. Presented at IEEE Current Measurement Technology Conference, March 2003. Towing Basin Speed Calibration of Acoustic Doppler Current Profiling Instruments by H. H. Shih, C. Payton, J. Sprenke, and T. Mero; NOAA/ National Ocean Services Analysis of Open-Channel Velocity Measurements Collected With an Acoustic Doppler Current Profiler by Juan A. Gonzolez-Castro, Charles S. Melching, and Kevin Oberg. Proceedings from the 1st International

pg. 57 of 85

Conference On New/Emerging Concepts for Rivers. Organized by the International Water Resources Association, September 22-26, 1996, Chicago, Illinois, USA. Effect of Temporal Resolution on the Accuracy of ADCP Measurements by Juan A. Gonzolez-Castro, Kevin A. Oberg, and James J. Duncker The following papers were published and presented by USGS personnel at the Hydraulic Measurements and Experimental Methods Conference (HMEM), Estes Park, Colorado, July 29 - August 1, 2002. For more information on the conference, visit the conference Web pages. Field Assessment of Acoustic-Doppler Based Discharge Measurements by David S. Mueller A Preliminary Evaluation of Near-Transducer Velocities Collected with Low-Blank Acoustic Doppler Current Profiler by Jeff Gartner and Neil Ganju Use of Acoustic Doppler Instruments for Measuring Discharge in Streams with Appreciable Sediment Transport by David S. Mueller In Search of Easy-to-Use Methods for Calibrating ADCP's for Velocity and Discharge Measurements by Kevin Oberg Use of an Acoustic Doppler Current Profiler (ADCP) to Measure Hypersaline Bidirectional Discharge by Kevin K. Johnson and Brian L. Loving

pg. 58 of 85

Appendix 5

Example Reports on Instrument Testing and Comparison by NHS’s

Due to size and formats, these documents could not be included within the report.

Please see report attachments Appendices 5a, 5b, 5c, 5d, 5e Appendix 5a): Comparison Measurements between SonTek FlowTracker Acoustic Doppler Velocimeter

and Price Current Meters, Water Survey of Canada* Appendix 5b): Field Assessment of Acoustic Doppler Based Discharge Measurements, David S. Mueller,

USGS Appendix 5c): Validation of Streamflow Measurements Made with Acoustic Doppler Current Profilers,

Kevin Oberg and David S. Mueller, USGS** Appendix 5d): Comparison of Bottom Track to Global Positioning System Referenced Discharges

Measured Using An Acoustic Doppler Current Profiler, Chad Wagner and David S. Mueller, USGS**

Appendix 5e): Summary of 2007 California District ADCP Check Measurements, Sacramento River at

Colusa CA, USGS** * Used with the permission of the Water Survey of Canada ** Used with the permission of the USGS; taken from the USGS OSW website reference documents as per Appendix 4.

http://www.wmo.int/pages/prog/hwrp/Flow/flow_tech/task4/Appendix5e_California-ADCP-Check-2007.pdf

http://www.wmo.int/pages/prog/hwrp/Flow/flow_tech/documents/task4/Appendix5a_Flowtracker-AA_Comparison.pdf

http://www.wmo.int/pages/prog/hwrp/Flow/flow_tech/documents/task4/Appendix5b_Field_HA_Analysis.pdf

http://www.wmo.int/pages/prog/hwrp/Flow/flow_tech/documents/task4/Appendix5c_HA-AA_Validation.pdf

http://www.wmo.int/pages/prog/hwrp/Flow/flow_tech/documents/task4/Appendix5d_Bottom_Track-GPS_Comparison.pdf

http://www.wmo.int/pages/prog/hwrp/Flow/flow_tech/documents/task4/Appendix5e_California-ADCP-Check-2007.pdf

pg. 59 of 85

Appendix 6

Example Report(s) on Verification of Performance as per Manufacturers Stated Specifications

Due to size and formats, this document could not be included within the report. Please see report attachment Appendix 6a.

Appendix 6a): Evaluation Report for Perfect Sensor Model 007 Pressure and Temperature Sensor and

Datalogger, USGS (Janice: can we have a real report for this appendix?)

**Used with the permission of the USGS

http://www.wmo.int/pages/prog/hwrp/Flow/flow_tech/documents/task4/Appendix6_Evaluation-of-Perfect_Sensor_Model-007-Data-Logger.pdf

pg. 60 of 85

Appendix 7

Examples of Water Level Sensor Calibration Procedures

To be completed

pg. 61 of 85

Appendix 8

Examples of Calibration Protocols for Vertical-Axis Velocity Current Meters

Appendix 8a): Calibration of Vertical-Axis Type Current Meters* Appendix 8b): Rating of Current Meters*

Appendix 8c): Spin Test for Vertical-Axis Velocity Current Meters*

* As downloaded from USGS public web site of published reports

pg. 62 of 85

Appendix 8a

Calibration of Vertical-Axis Type Current Meters

As extracted from Calibration and Maintenance of Vertical-Axis Type Current Meters”, U.S. Geological Survey, Techniques of Water-Resources Investigations, Book 8, Chapter 2, By George F. Smoot and Charles E. Novak, 1977

The principal of operation of a rotating-element type velocity meter is based on the proportionality between the local flow velocity and the resulting angular velocity of the meter rotor. The velocity of the water is determined by counting the number of revolutions of the rotor during a measured interval of time and consulting the meter calibration table. If an ideal current meter, that is, one equipped with a correctly shaped rotor and a frictionless bearing mechanism, were to measure the flow velocity of a perfect liquid, the relation between the flow velocity and the rotor speed would be very simple :

V=KN (1) where V denotes the local flow velocity, K is the proportionality constant, and N is the rotor speed expressed in revolutions per unit of time. In actual practice there are resistances opposing rotation caused by friction between the liquid and the rotor and by the mechanical friction of the bearings. Consequently, this simple relationship does not exist, and one must be determined empirically. The establishment of this relation, known as “rating the current meter,” is done for the Survey by the National Bureau of Standards. The current-meter rating station operated by the National Bureau of Standards in Washington, D.C., consists of a sheltered reinforced concrete basin 400 feet long, 6 feet wide, and 6 feet deep. Atop the vertical walls of the basin and extending its entire length are steel rails that carry an electrically driven rating car. This car is operated to move the current meter at a constant rate through the still water in the basin. Although the rate of travel can be accurately adjusted, the average velocity of the moving car is determined for each run by making an independent measurement of the distance it travels during the time that the revolutions of the bucket wheel are electrically counted. A scale graduated in feet and tenths is used for this purpose. A small Price meter is rated by towing it at eight different velocities (0.25, 0.50, 0.75, 1.10, 1.50, 2.20, 5.00, and 8.00 feet per second). A pair of runs are made at each velocity. A pair consists of two traverses of the basin, one in each direction. The data obtained consists of 16 observations of the velocity of the car (V) and revolutions per second of the rotor (N). The meter rating is determined from these data and is expressed as two linear equations :

For N less than 1.00, V = K1N + C1 (2)

For N greater than 1.00,

V = K2N + C2 (3)

where K2 = K1 + C1- C2 (4)

Because there is rigid control in the manufacture of the small Price meter, virtually identical meters are produced and, for all practical purposes, their rating equations are identical. Therefore, there is no need to calibrate each meter individually. Instead, a standard rating is established by calibrating a large number of meters that have been constructed according to Survey specifications, and this rating is then supplied with each meter. To insure that all small Price meters are virtually identical, dies and fixtures for their manufacture were purchased by the Water Resources Division and supplied to the manufacturer in 1967 for use in constructing meters. These same dies and fixtures will be supplied to the successful bidder in subsequent years. All rotors manufactured by use of the standard dies and fixtures are stamped “S” on

pg. 63 of 85

the top side of the bucket wheel. The year of manufacture is also identified-S-67, S-68, for example. To further insure that all meters are identical, quality control procedures are followed, including the rating of a sample of meters from each new group procured. For convenience in field use, the data from the current-meter ratings are reproduced in tables, a sample of which is shown in figure 3. The velocities corresponding to a range of 3-350 revolutions of the bucket wheel within a period of 40-70 seconds are listed in the table. This range in revolution and time has been found to cover general field requirements. To provide the necessary information for the few instances where extensions are required, the equations of the rating table are shown in the spaces provided in the heading. Because of limited space, the equations are presented in an abbreviated form. The expression V = 2.14ON + 0.015 (2.155), V = 2.150N + 0.005 shown in the heading of the table in figure 3 is to be interpreted as follows:

V represents velocity in feet per second.

N represents the number of revolutions of the bucket wheel per second.

That part, V = 2.14ON + 0.015, to the left, of the parentheses is the equation used for computing velocities shown in the table less than 2.155 feet per second.

That part, V = 2.15ON + 0.005, to the right of the parentheses is the equation used for computing the values for V more than 2.155 feet per second.

The term within parentheses (2.155) is the velocity common to both equations.

Data do not indicate that there is any significant difference between a rod rating and a cable suspension rating when Columbus-type weights and hangers are properly used with the meter. Therefore, no suspension coefficient is indicated, and none should be used.

pg. 64 of 85

Appendix 8b

Rating of Current Meters

As extracted from USGS Open File Report 99-221: Quality Assurance of U.S. Geological Survey Stream Current Meters: The Meter-Exchange Program 1988-98

The USGS uses, with few exceptions, a standard rating for each type of current meter. These ratings are based on equations that relate the rotational velocity of the current-meter bucket wheel to the velocity of the water. Two equations define the range of velocities in which AA meters are used. These equations yield the same water velocity at 2.2 feet per second (fps), which is 1 revolution per second of the bucket wheel. Below 2.2 fps one equation is used; above that velocity, the other is used. For pygmy meters the entire range of velocity is defined by a single equation. The equations for each type of meter are converted to look-up tables (rating tables) for use in the field. Using a current-meter rating table, a hydrographer can convert observations of the number of revolutions of the meter bucket wheel in a given number of seconds directly into water velocities. Before 1980 for pygmy meters and before 1970 for AA meters, each USGS current meter was rated separately and was issued with an individual rating table. Smoot and Carter (1968) showed that, within groups of meters from each of three manufacturers, an average (standard) rating gave nearly as accurate results as individual ratings. Subsequently, Schneider and Smoot (1976) demonstrated for pygmy meters that little additional error (generally a fraction of 1 percent) resulted from using a standard rating rather than individual meter ratings. These and other similar investigations provided an opportunity for cost savings. If meters have nearly identical physical dimensions and responsiveness, then random samples can be tested, and thus avoid calibrating every meter in a batch of new meters. Use of standard ratings also permits replacement in the field of a principal component of a current meter, such as a bucket wheel, without having to have the meter recalibrated. To determine if the responsiveness of a meter (in an "as-received" condition from the field or new from a manufacturer) is accurately described by an appropriate standard-rating equation, it is necessary to calibrate the meter in a tow tank or similar device. In a tow tank, a meter is towed horizontally through a long tank of still water where the number of bucket-wheel revolutions is recorded over very precisely measured distances and times. The meter is towed in both directions through the tank at each of several nominal calibration velocities to cover much of the range of velocities to be measured with the meter type. Averaging the calibration data in both directions ensures that they are not affected by any currents that may exist in the tank. These procedures are specified in more detail in the international standard, "Liquid flow measurement in open channels--Calibration of rotating-element current-meters in straight open tanks", (International Organization for Standardization, 1976) (writer’s note: this standard replaced in 2007 by ISO 3445 Hydrometry – Calibration of Current Meters in Straight Open Tanks). The USGS calibrates about 10 percent of the meters that are received in a batch from a manufacturer by using a tow tank in the Office of Surface Water Hydraulic Laboratory at Stennis Space Center, Mississippi. If one meter from the sample fails to meet the criteria established for meter accuracy, another 10 percent of meters from the batch is calibrated. If any more meters fail to meet the criteria, then the entire batch of meters is calibrated, and only those that meet the accuracy criteria are accepted. (E. C. Hayes and D. R. Meyers, USGS Hydrologic Instrumentation Facility, written commun., 1998). The accuracy criteria relative to the true velocity that is measured in the calibration process, are as follows:

pg. 65 of 85

Table 1: Accuracy criteria for Price type AA and pygmy current meters

Price AA current meter Price pygmy current meter Velocity, in feet per second

Accuracy criterion, in percent

Velocity, in feet per second

Accuracy criterion, in percent

0.25 +/- 6.0 0.25 +/- 6.0 0.50 +/- 3.4 0.50 +/- 3.4 0.75 +/- 2.5 0.75 +/- 2.5 1.10 +/- 2.0 1.50 +/- 1.8 1.50 +/- 1.5 2.20 +/- 1.5 2.20 +/- 1.0 3.00 +/- 1.5 5.00 +/- 1.0 8.00 +/- 1.0

These accuracy criteria are based on much experimental data and have a statistical basis. The criteria are set at about 2 standard deviations of published current-meter calibration data (Smoot and Carter, 1968; Schneider and Smoot, 1976; and W.H. Kirby, written commun., 1998). Current meters that are subsequently calibrated meet the criteria if their velocities predicted from the appropriate standard rating falls within the plus or minus limits of the true velocity, which is measured during the calibration process. About 95 percent of current meters are expected to meet the criteria shown in table 1, if the calibration data are normally distributed and the standard rating is an accurate measure of the average responsiveness of the meters tested. International standard "Assessment of uncertainty in the calibration and use of flow measurement devices-Part 1: Linear calibration relationships," which was issued by The International Organization for Standardization (1989), also establishes the 2-standard-deviation criteria as being appropriate for calibration of current meters. The accuracy criteria for whether a meter passes or fails in regard to the true velocity are applied with considerable judgment and latitude. If the standard rating does not predict (based on the rotational velocity of the bucket wheel) the actual velocity within the criteria at one calibration- data point, the possibility of a laboratory error is explored. If miscounting by the instrument that counts the bucket-wheels rotations is detected when inspecting the data, that data point is deleted or corrected to permit the meter to pass. If there are still one or more calibration-data points that are not within the criteria but are close (within about one tenth of a percent), the relationship between rotational velocity and water velocity that is defined by the individual meter's calibration data is generated. If this resulting equation (or equations in the case of the AA meters) plots within the accuracy criteria, the meter is judged to have passed, even if a calibration-data point or two is outside the limits. Finally, the rounding of the accuracy criteria as used in the laboratory software is such that the limits are slightly larger than those shown in table 1. For example, the working criteria for the three faster velocities for the AA meter effectively has been 1.1 percent, instead of 1.0 percent (table 1). The USGS counterparts in Environment Canada do not use standard ratings. Although they principally use the AA and pygmy meters, the Canadians feel it necessary to rate each meter individually. The meters that the Canadians use are periodically recalled to their hydraulic laboratory in Burlington, Ontario, to be rebuilt and re-rated (DeZeeuw and Bil, 1975). The laboratory also performs this function for meters owned by Canadian provinces, hydro-power companies, and others. Contribution of Instrument Error to Discharge-Measurement Error Instrument error is only one of several significant errors that may contribute to the overall error of a discharge measurement. Sauer and Meyer (1992) found that most measurements of discharge by current meters will have standard errors ranging from 3 to 6 percent. Poor measuring conditions (such as very slow water velocities or shallow depths) or improper procedures of meter use, however, can result in much larger errors. They cited important sources of error--other than the error contributed by the current

pg. 66 of 85

meter--such as the measurement of depth, the pulsation of flow, the vertical distribution of velocities, the measurement of horizontal angles, and the computations involving the horizontal distribution of velocity and depth (insufficient number of or inadequate measuring subsections). Sauer and Meyer estimated the total error of discharge measurements by taking the square root of the sum of the squares of the individual errors contributed by the various sources of error. The error associated with the current meter, which Sauer and Meyer termed "instrument error", was relatively small (0.3 percent) for AA meters used under ideal measuring conditions and following the recommended field procedures. For pygmy meters, the instrument error they used was still relatively small at 0.8 percent for a wading measurement with good field conditions. Their analysis properly used the standard error of estimate, which is 1 standard deviation of the calibration data used to develop the standard rating. Sauer and Meyer did not consider the case of a meter whose difference from the standard rating is near to or falls outside of the accuracy criteria, which is 2 standard deviations. Such a meter could contribute an instrument error up to about twice as large as they used. In poorer field conditions where the velocity is slow, Sauer and Meyer found meter error to be a large source of error with respect to the other sources. Here again, they used the standard error of 1, not 2, standard deviations as the instrument error. The errors associated with individual discharge measurements contribute to the error of the rating curve, which is the graphical relationship between stage and discharge for a streamflow gaging station. The rating-curve error is incorporated directly in the discharges that are computed and published for a station. If several meters were employed in the development of the rating curve, instrument errors might off-set each other. This does not always happen in practice, however. Sometimes long periods go by when one meter is predominately used to define the rating curve. Thus, any error in velocity data that is introduced by a current meter would be of concern.

pg. 67 of 85

Appendix 8c

Spin Test for Vertical-Axis Velocity Current Meters

As extracted from Calibration and Maintenance of Vertical-Axis Type Current Meters”, U.S. Geological Survey, Techniques of Water-Resources Investigations, Book 8, Chapter 2, By George F. Smoot and Charles E. Novak, 1977

The spin test is an easy method of determining the condition of the bearings of a current meter. In making this test, the meter should be placed so that the shaft is in a vertical position and the bucket wheel is protected from air currents. The bucket wheel is then given a quick turn by hand to start it spinning, the duration of which is timed with a stopwatch. As the rotating bucket nears the stopping point, its motion should be carefully observed to see whether the stop is abrupt or gradual. Regardless of the duration of the spin, if the bucket wheel comes to an abrupt stop, the cause of such behavior should be found and corrected before the meter is used. In such instances, a lack of oil, the maladjustment of the penta gear, and a misalignment of the yoke are possible sources of trouble that should receive early attention. The normal spin for a small type-AA Price should be approximately 4 minutes and should under no circumstances be less than 1% minutes. Large variations in the duration of the spin test will be introduced by slight variations from the vertical position of the shaft. Some operators accordingly provide themselves with a small circular level vial that can be placed on the cap of the meter t6 help them make such a test with the shaft aligned in a truly vertical position. Another common test to determine the condition of the bearing of a current meter is to hold the meter so that the shaft is in a vertical position and while keeping the shaft in as nearly a fixed position as possible, to revolve the yoke and tailpiece in a horizontal plane around it. If the bucket wheel remains in a fixed position, it is an indication that the bearings are satisfactory, whereas if the bucket wheel tends to revolve with the yoke and tailpiece, it is an indication that the meter requires attention.

pg. 68 of 85

Appendix 9

Example Procedures for Checking Calibration of Acoustic Doppler Instruments

Appendix 9a): Field Checks for TRDI ADCP Instruments* Appendix 9b): Diagnostic Tests and Field System Checks for Sontek Flowtracker* Appendix 9c): Tow Tank Calibration Checks for Sontek FlowTracker AVM** Appendix 9d): Diagnostic Checks for Sontek FlowTracker AVM** Appendix 9e): Application of the Loop Method for Correcting Acoustic Doppler Current Profiler

Discharge Measurements Biased by Sediment Transport**

Appendix 9f): List of USGS Hydroacoustic Current Policy Memorandums related to the use of hydroacoustic technologies**

* Used with the permission of the Water Survey of Canada ** Used with the permission of the USGS.

http://www.wmo.int/pages/prog/hwrp/Flow/flow_tech/documents/task4/Appendix9c-USGS_OSW2010-02_Flowtracker_Calib.pdf

http://www.wmo.int/pages/prog/hwrp/Flow/flow_tech/documents/task4/Appendix9d-USGS_OSW2010-06_Flowtracker_Diag.pdf

http://www.wmo.int/pages/prog/hwrp/Flow/flow_tech/documents/task4/Appendix9e-USGS_Loop_Method_Application_SIR2006-5079.pdf

pg. 69 of 85

Appendix 9a

Field Checks for TRDI ADCP Instruments

As extracted, with minor editing, from Water Survey of Canada’s SOP001-01-2004 Procedures for Conducting ADCP Discharge Measurements, First Edition, 2004

and ADCP Maintenance, Appendix to SOP001-2004 Two types of assessments must be performed as part of the recommended ADCP maintenance:

1. Routine assessments done prior to each measurement, and 2. Periodic assessments done at pre-determined intervals

1. Routine Instrument Assessment To be performed prior to every measurement General Instrument Integrity Inspect the ADCP to assess the general condition of its enclosure, transducer head, communication and power cables. This is a visual inspection to detect mishandling, use of chemicals, abrasive cleaners, and excessive depth pressures that may have resulted in damage. Inspect transducer faces for dents, chipping, peeling, urethane shrinkage, hairline cracks and damage that may affect watertight integrity or transducer operation. Send the ADCP for repairs if seemingly important defects are observed. Health of Internal Electronics Internal properties and electronic responses are assessed via a series of internally built performance and testing commands. Step 1: control the test environment During the tests ensure that:

• The transducer faces are fully submerged in water • The test is done in calm waters (water bucket or vessel at drift in quiet eddy) • All acoustical and high power equipment are powered down during testing • ADCP is more than 1 m away from electromagnetic interferences

Step 2: Open WinRiver II and under the acquire menu click “Execute ADCP test”. Note any failures: If the failure occurs with the following parts of the RG Test:

1. CPU 2. Recorder (Communication, DOS Structure, Sector Test) 3. DSP 4. System Test (XILINKS Interrupts)

Re-run the test 2 more times ensuring again that there are no external sources of interference. If you get repeated failures on the 3 tries send the ADCP for inspection and repair. If you see a fail on the following parts of the ADCP test, they warrant further investigation before returning the ADCP to the manufacturer.

5. Wide and Narrow Bandwidth. Usually fails due to environmental conditions. Avoid being too close to strong electromagnetic sources such as power supplies, CRT Screens, RF Radios, etc.

6. RSSI Filter. Usually fails due to external interference. Turn off all devices with frequencies in the 300KHz to 3MHz range., increase distance between the ADCP and strong noise sources (significant electromagnetic emitters) potentially interfering in the vicinity.

7. Transmit. Usually fails when the test is not performed in water. 8. Ambient temperature probe .

pg. 70 of 85

Repeated failure of tests 5, 6 and 7: Perform a beam continuity test (rub test) (Refer to Beam Continuity, p. 7 in the Workhorse Test Guide). This test is used to verify that the transducer beams are connected and operational. It requires a measure of Receiver Signal Strength Indicator (RSSI) levels while transducer faces are rubbed vigorously. • Verify that no device operating

nearby may be a source of electromagnetic interferences.

• Perform all tests while the transducers submerged.

• All beams must pass. A defective transducer beam can also be detected while collecting data. The echo intensity of the defective beam may be weaker than others. See figure 1. System problems detected in tests 5, 6 and 7 can also be detected by collecting data at the site. Looking at Intensity profile as depicted in Figure 1, there should be >120 counts at the top bin (closest to the transducer) and, if there is full range of water in front of the ADCP, it should decrease all the way down to 20-50 counts (end of range). In this way, when aforementioned criteria are not met, it is not possible to know whether it is the Receive or Transmit path that fails. Prior to actually sending the instrument for servicing, send the results of several predeployment tests to the manufacturer for advice on servicing needs. Repeated failure of test 8: The Ambient temperature probe is highly suspect when there is constantly more than 2 ºC difference between the water temperature measured by the ADCP and a standard thermometer1 measurement. Ensure that the ADCP has had sufficient time to acclimatize to the water temperature(This may take up to xx minutes). If the probe seems to fail, enter the value taken with a standard thermometer as manual override for the computations in WinRiver. Back from the field, retest the unit and send it to be examined if the problem persists. Note that a shorted temperature sensor will report 92 ºC and an opened sensor will report -37 ºC or less. Compass Calibration Calibrating the internal compass is always required when using a GPS. Data can be collected without calibration if there is no detected moving bed. To calibrate the compass, follow the instructions in the TRDI Workhorse Rio Grande ADCP Technical Manual, or the One-cycle Compass Correction Method 3 described in the WinRiver help file under “How Do I Use GPS/Compass Correction. To do so, in BBTalk start logging a file (save it with in the folder created using the file naming convention) and send the AF command (type AF and press enter). From the menu displayed, choose C and then A. Rotate the boat on a complete circle. Once back to the initial heading, the system will calculate corrections to use for the magnetic field present at the site. Complete the calibration by entering D and then hit any key. Confirm the compass calibration by sending the AX command and again rotating the boat on itself to make a complete circle. While doing this calibration:

a. Make sure there is no ferrous material, such as a steel hull or mounting frame, in the vicinity of the ADCP which would disturb the internal magnetic compass.

1 A standard thermometer is a calibrated thermometer accurate to +/- 0.2 °C

Figure 1. Lower Intensity from Defective beam

pg. 71 of 85

b. It is the AF command that improves and stores compass corrections. If the resulting total compass error is too high, above 4 degrees, it is this command that should be repeated in this process. Once satisfied, the AX command will further evaluate the correction accuracy.

c. While proceeding with the test, changes in pitch and roll must be avoided. Turning the boat in steady location rather than doing large loops will reduce the likelihood of swaying in the boat’s own wake.

d. Maximum rotation velocity for best results is 5 degrees per seconds. Repetitive closure of no better than 4 degrees in the compass performance evaluation may indicate a failure to calibrate the system. If it is not possible to have better closure after several attempts at any given site (calm water, no change in pitch and roll), retest the system in an area with little potential for local magnetic disruptions while also ensuring that nothing aboard may interfere with the compass precision (e.g. ferrous material). If calibration cannot be achieved within the prescribed threshold, send the unit for servicing. 2. Periodic Instrument Assessment Servicing Each ADCP must be returned to the manufacturer and serviced every 3 years to perform a desiccant replacement, an inspection of enclosure, lubrication of O-rings and grooves, and assure the overall functionality of electronics and transducers. A service date sticker should be displayed on each instrument or each instrument case. Computation Characteristics Information that defines ADCP velocity computations is stored directly within the instrument memory. This information is secure but to ensure that it is not unduly modified, it should be recorded prior to and after any changes to hardware or firmware, such as when:

1. Sending an ADCP for servicing 2. Upgrading the ADCP firmware

To record the computation characteristics:

• Establish a direct connection with the ADCP. • Start logging data - include the serial number and date in the file name. • Enter the following commands, pressing enter after each one:

1) CR1 (Parameters set to factory defaults) 2) CK (Parameters saved as user defaults) 3) PS0 (Offsets, versions and serial numbers) 4) PS3 (Beam characteristics, directional matrix and transformation matrix) 5) OL (Installed features)

• Stop logging data. When receiving the ADCP after servicing or after upgrading the firmware, again record the characteristics as above and compare to the previously recorded values. Any unexpected changes (i.e. something other than user defaults and version number after a firmware upgrade) are to be documented and reported. Beam Alignment Every ADCP uses a unique system of coordinate-transformation matrices to perform its computations. If an ADCP displays beam alignment errors, then it is likely that the Instrument Transformation matrix and the Beam Directional matrix are not suitable for the instrument. The purpose of this process is to determine and document the presence of beam alignment errors. Each ADCP used by WSC offices must be tested:

1. When the equipment is received from the manufacturer 2. After a situation leading to potential damage that might have resulted in changes to beam

alignment 3. At least once every 3 years

pg. 72 of 85

Requirements:

• ADCP Mount that can be rotated about the vertical axis • DGPS with sub-meter accuracy (RTK recommended) and an output frequency matching the

ADCP ping rate. • 500 m straight course with regular bed for accurate bottom track data

o No moving bed o No debris on the bottom o Not too shallow nor too deep

• Slow(<0.2m/s??) or no water velocity and no waves ADCP Preparation:

• Use water mode 1 with bottom mode 5 or 7, depending on depth at site. Make sure to only use single pings (BP1, WP1).

• Use a GPS frequency that allows recording at least as many positions from bottom track as from the GPS receiver. 1. Perform standard diagnostic tests (e.g., Execute ADCP Test). 2. Calibrate the compass.

Process:

1. Mount the ADCP with beam 3 forward. 2. Choose a heading that will allow a straight trajectory of at least 500m on a straight line. It is

good practice to mark the selected path with a buoy at both ends. 3. Start recording once at cruising speed. Drive with constant heading for at least 500 meters

as shown in Figure 1 (maintain a steady speed with little acceleration to minimize error from internal sensors). Monitor the course heading and keep it constant. Ensure that bottom tracking quality is adequate throughout the course.

4. Stop recording and document the ratio of the bottom-track course made good to the GPS course made good, BC/GC.

a) A value close to 0.998 and 0.999 is desired for well calibrated ADCPs. b) Results must fall between 0.995 and 1.003. c) Rotating the ADCP helps to identify what transducers are misaligned if any. d) Bottom tracking typically has a slight negative bias caused by terrain bias. Experience

to date (Oberg, 2002) has shown that when the bottom track to GPS ratio is less than 0.995, ADCP measurements most likely have a negative bias error, and when the bottom track to GPS ratio is greater than 1.003, the ADCP most likely has a positive bias error.

5. Redo steps 3 and 4 while returning to the start point of the previous record. 6. Once the reciprocal heading transect is complete, rotate the ADCP clockwise by 45 degrees

in its mount and restart the process from step 3. Repeat the entire process until the ADCP has been rotated 4 times, for a total of 8 recorded transects as follows:

a) Two transects with beam 3 facing forward, b) Two transects with beam 3 at 45º clockwise, c) Two transects with beam 3 at 90º clockwise, and d) Two transects with beam 3 at 135º clockwise

Documentation: Two forms for documenting the distance tests are shown in the appendices: • The first is a field form for use when completing the beam misalignment tests. Record the results of

each pass on this form. For each beam orientation used, the bottom track to GPS ratio should be computed as the mean of the two reciprocal passes made.

• The second form is an Instrument History Form used to describe completed tests, firmware upgrades, and repairs and servicing.

A paper or electronic copy of these forms should be maintained in an office file.

pg. 73 of 85

Reference: • WSC’s SOP001-2004 Procedures for Conducting ADCP Discharge Measurements • WSC’s SOP002-2004 Procedures for Review and Approval of ADCP Discharge Measurements • U.S. Geological Survey ADCP Training, “S21a - Beam Alignment Errors.ppt”. E-mail

communication with David S. Mueller, May 2005. • U.S. Geological Survey, OFFICE OF SURFACE WATER TECHNICAL MEMORANDUM 2006.04,

‘Instrument Tests for ADCPs Used for Velocity and Streamflow Measurements’, Mail Stop 415, Draft.

• WorkHorse Commands and Output Data Format, P/N 957-6156-00 (August 2001) • WorkHorse Test Guide P/N 957-6154-00 (January 2001) • Workhorse Troubleshooting Guide, P/N 957-6155-00 (January 2001)

pg. 74 of 85

FIELD NOTES FOR BEAM MATRIX TEST

Location: Date Party

Manufacturer Model Frequency Serial # Firmware Software Filename Prefix: ADCP Draft Diag. Test y / n Bottom Mode Water Mode Other Configuration Commands: Boat/Motors Used: ADCP Water Temp Measured Water Temp GPS Used: Moving Bed Test File Moving Bed? y / n Describe measurement site: Weather Streambed material Salinity Max Water Depth Max Water Speed Max Boat Speed Orientation Heading File # Field BT/GT Notes 3 forward Reciprocal 3 clockwise 45º Reciprocal 3 clockwise 90º Reciprocal 3 clockwise 135º Reciprocal Respects Threshold (0.995 < BT/GT < 1.003)? y / n Comments: Sheet # of sheets

pg. 75 of 85

Instrument History Form

Instrument Manufacturer: Model: Frequency:

Serial Number: Purchase Date: Log: (Description of Test or Upgrade or Maintenance, Name, Date, Comments)

pg. 76 of 85

Appendix 9b

Diagnostic Tests and Field System Checks for Sontek Flowtracker

As extracted, with minor editing, from Water Survey of Canada’s SOP-NA022-03-2011 Procedures For Conducting Discharge Measurements With Sontek Flowtracker Acoustic Doppler Velocimeters,

Rev. 3, 2011 DIAGNOSTIC TESTS There are two types of diagnostic tests for the FlowTracker. One test is an Automatic Quality Control Test done in the stream prior to each measurement. The second type of diagnostic test is a BeamCheck (or bucket test) that is similar to the Auto QC test but offers more detailed diagnostics. 1. Automatic QC Test The Automatic QC Test (SmartQC) is a simplified and automated version of the BeamCheck that can be run in the field. The Automated QC Test must be conducted prior to the start of every measurement. Run the Automated QC Test when prompted at the beginning of each data file for your measurement, so that results are recorded and can be archived and reviewed at a later date. It is possible to run the Automated QC Test manually from the “System Function” menu prior to starting a measurement but in this case, the results are displayed to the user but not recorded. A BeamCheck should be conducted if the Automatic QC Test identifies any warning. 2. BeamCheck (Bucket Test) To document the baseline performance of the FlowTracker, a BeamCheck (bucket test) must be performed in a controlled environment using the BeamCheck application within the FlowTracker software. For a more detailed description of BeamCheck see section 6.5 in the FlowTracker technical manual. a) When to run BeamCheck The BeamCheck is to be performed in a controlled environment on all FlowTracker units when:

• a unit is new and received from the manufacturer; • after a firmware upgrade or repair of unit; • anomalies or failures are noticed in the auto QC test done prior to every measurement; • after any physical damage (drop, etc).

b) How to run BeamCheck Establish a controlled environment using the following criteria:

• Container Type: Plastic or non ferrous metal. • Container Dimensions: Large enough to allow 0.2 to 0.3 meters from central sensor face to

opposite container wall. • Water Depth: Minimum depth of water in container, 0.2 meters. • Test duration: Minimum 20 pings.

Hold FlowTracker probe in a pail of water and have the boundary or pail side within 20-30 cm of the face of probe. Connect FlowTracker to computer and run software. It may be necessary to seed the water in the container with some fine-grained material to provide sufficient return signals. After establishing

pg. 77 of 85

communication with the FlowTracker, a diagnostic menu appears. Select BeamCheck then select Start and then Record. Pick the file location. Create folders on the server named; BeamCheck Record\”FlowTracker Serial Number”. The naming convention is: YYYYMMDD_”FlowTracker Serial Number”.bmc. Record a minimum of 20 pings, which is shown in the top left of window, and then click Stop. c) View & Archive Test Records BeamCheck results can only be viewed with FlowTracker software. For this reason, the test results page generated from each FlowTracker must be saved as a screen capture as shown in Figure 7 below.

• BeamCheck Test record results can be viewed using the BeamCheck application in FlowTracker software. Select ‘Open file’, select the required file and then select ‘Replay’.

• Use the menu and control items to alter the display of data as desired. The recorded data is not affected; only the display of data. See the technical manual, accessible from the FlowTracker software, for more explanation of the BeamCheck results.

• To determine the FlowTracker sampling volume location, replay the recorded BeamCheck with averaging on. The location is graphically indicated by the peak in the bell-shaped curve 10-15 cm from the transmitter and numerically in the Peak Pos (cm) table for each beam. The distance to peak should be similar for the two beams, but if not, average them together to get the distance of the measuring volume from the transmitter face. This distance is used to set the sampling volume locator on the alignment tool and will be unique for each FlowTracker. This distance will be rounded to the nearest half centimeter.

The BeamCheck screen capture contains all the baseline information for the individual FlowTracker and both hard copy and electronic versions are to be archived.

1. The screen capture is saved as a Word document and a hard copy is created and archived in the QMS reference files within the folder titled FlowTracker Performance Records. The naming convention for the screen capture of the electronic file is: YYYYMMDD_FlowTracker Serial Number_bmc.doc

2. The electronic file is archived on a server in a folder named BeamCheck Record. The naming

convention for the electronic file generated with the FlowTracker software is: YYYYMMDD_FlowTracker Serial Number.bmc.

Figure 7. Example of BeamCheck screen capture

pg. 78 of 85

Do not use the FlowTracker if results from this test display any of the following issues. See Figures 8, 9, 10. (ref. FlowTracker Technical Manual, 6.5.4 BeamCheck Operation):

• Malfunctioning transmitter Results translate into a flat signal response (very low SNR) if the water is too clear or if the transmitter is malfunctioning. You may need to “seed” the test water to verify results.

• Malfunctioning receiver(s)

Results display unequal peak amplitudes of 10 to 20 counts or more. First, make sure the transducer faces are clean and verify results.

• Damaged/bent receiver arms

Results show a shift in peak positions between the two signals. If the peak positions differ by more than 1.5 cm, note the difference and do not use the FlowTracker.

• Excessive noise or high signal strength beyond boundary

Noise more than 10 counts above the instrument level or a signal strength that remains high at a distance that correspond to a location outside of the tank boundary may indicate a problem with test conditions. Change/modify the testing container and retry BeamCheck to confirm that the problem is with the probe.

Figure 8 Typical BeamCheck Profile (Sontek FlowTracker Technical Manual)

pg. 79 of 85

Figure 9 Malfunctioning Transmitter (Sontek FlowTracker Technical Manual)

Malfunctioning Receiver (Sontek FlowTracker Technical Manual)

Excessive Noise (Sontek FlowTracker Technical Manual)

Bent Receiver Arm (Sontek FlowTracker Technical Manual)

High Signal Strength beyond Boundary (Sontek FlowTracker Technical Manual)

Figure 10 Other Examples of BeamCheck results

pg. 80 of 85

FIELD SYSTEM CHECKS Check the following parameters prior to every measurement:

• Batteries: capacity at sufficient levels. Check the battery voltage once the system has acclimatized to the site temperature. The FlowTracker will not collect data unless the input voltage is at least 7.0 V. If voltage drops below 8.0 V during data collection, the FlowTracker will provide a warning message. Stop data collection and replace the batteries to prevent loss of data.

• Clock date and time: adjusted to local requirements.

All data will be time stamped according to this internal clock.

• Probe recorded temperature: verified against a calibrated thermometer. A calibrated thermometer measurement must be collected. The temperature reported by the FlowTracker should fall within 2oC of the value measured by a calibrated thermometer once allowed to acclimatize to local conditions. If a larger difference persists, the FlowTracker calibration is suspect. Continue and complete the measurement. However, after the measurement, the discharge must then be corrected to account for the temperature difference. The FlowTracker should be sent for servicing. If the air temperature is significantly warmer or cooler than the water temperature, regular monitoring of the probe temperature throughout the measurement is recommended to ensure that the estimated speed of sound in water is not affected by the probe being exposed to the air between panels. Before leaving the site, it is recommended to view the time series plot of temperature using the DatView software to confirm it is within acceptable limits.

• Raw velocities: in agreement with visual inspection.

Raw velocities should be consistent with observed conditions at the test point, factoring the relative angles. Rotate the probe by 90o and verify that it results in a reversal of the velocity values Vx and Vy.

• Raw SNR: at required levels.

In general, all beams should show SNR values within 2 to 4 dB of each other. Raw values above 10 dB are desirable. Although the recommended minimum SNR values in the manual are 4dB, there has also been confirmation from Sontek that reasonable velocity values may be obtained at levels down to 2-3dB providing that values for standard error for velocity are not high. Users in low SNR environments should pay particular attention to other warnings related to the number of velocity spikes and especially standard error of velocity. A combination of low SNR and velocity-related warnings indicate the FlowTracker may be generating inaccurate water velocities. If the SNR values are below 4 dB for any beam, the measurement is suspect and requires extra scrutiny to justify acceptance of the acquired velocities.

pg. 81 of 85

Appendix 9c

Tow Tank Calibration Checks for Sontek FlowTracker AVM

In 2010, the USGS gained the in-house capacity to conduct tow tank calibration of Sontek Flow Trackers, and issued a policy regarding the submission of in-use Flow Trackers for calibration checks. This policy is captured in the USGS Office of Surface Water Technical Memorandum 2010.02: “Flow Meter Quality-Assurance Check - Sontek/Ysi Flowtracker Acoustic Doppler Velocimeter”

Due to size and format, this document could not be included within the report.

Please see report attachment Appendix 9c

http://www.wmo.int/pages/prog/hwrp/Flow/flow_tech/documents/task4/Appendix9c-USGS_OSW2010-02_Flowtracker_Calib.pdf

pg. 82 of 85

Appendix 9d

Diagnostic Checks for Sontek FlowTracker AVM

In 2010, the USGS issued an updated policy on diagnostic checks for Flow Trackers. It is captured in the USGS Office of Surface Water Technical Memorandum 2010.06:

“FlowTracker Diagnostic Test Policy”

Due to format, this document could not be included within the report. Please see report attachment Appendix 9d

http://www.wmo.int/pages/prog/hwrp/Flow/flow_tech/documents/task4/Appendix9d-USGS_OSW2010-06_Flowtracker_Diag.pdf

pg. 83 of 85

Appendix 9e

Application of the Loop Method for Correcting Acoustic Doppler Current Profiler Discharge Measurements Biased by Sediment Transport

The USGS, have developed an application called the “Loop Method” for adjusting discharge measurements affected by moving beds. This captured in the USGS Scientific Investigations Report 2006:5079 - Application of the Loop Method for Correcting Acoustic Doppler Current Profiler Discharge Measurements Biased by Sediment Transport, By David S. Mueller and Chad R. Wagner, 2006, prepared in cooperation with Environment Canada (Water Survey of Canada).

Due to size and format, this document could not be included within the report.

Please see report attachment Appendix 9e

The abstract for the above noted report, as downloaded from the USGS Hydroacoustic website, follows. A systematic bias in discharge measurements made with an acoustic Doppler current profiler (ADCP) is attributed to the movement of sediment near the streambed - an issue widely acknowledged by the scientific community. This systematic bias leads to an underestimation of measured velocity and discharge. The integration of a differentially corrected Global Positioning System (DGPS) to track the movement of the ADCP can be used to avoid the systematic bias associated with a moving bed. DGPS systems, however, cannot provide consistently accurate positions because of multipath errors and satellite signal reception problems on waterways with dense tree canopy along the banks, in deep valleys or canyons, and near bridges. An alternative method of correcting for the moving-bed bias, based on the closure error resulting from a two-way crossing of the river, was investigated by the U.S. Geological Survey. The uncertainty in the measured mean moving-bed velocity caused by nonuniformly distributed sediment transport, failure to return to the starting location, variable boat speed, and compass errors were evaluated using both theoretical and field-based analyses. The uncertainty in the mean moving-bed velocity measured by the loop method is approximately 0.6 centimeters per second. Use of this alternative method to correct the measured discharge was evaluated using both mean and distributed correction techniques. Application of both correction methods to 13 field measurements resulted in corrected discharges that were typically within 5 percent of discharges measured using DGPS.

http://www.wmo.int/pages/prog/hwrp/Flow/flow_tech/documents/task4/Appendix9e-USGS_Loop_Method_Application_SIR2006-5079.pdf

pg. 84 of 85

Appendix 9f

List of USGS OSW Hydroacoustics Current Policy Memos

Memo No. Subject

2012.01 Processing ADCP Discharge Measurements On-site and Performing ADCP Check Measurements

2011.08 Exposure Time for ADCP Moving-boat Discharge Measurements Made During Steady Flow Conditions

2011.04 Policy on the Use of Hydroacoustic Software and Firmware 2010.07 Independent Water Temperature Measurement for Hydroacoustic Measurements 2010.06 FlowTracker Diagnostic Test Policy

2010.02 Flow Meter Quality-Assurance Check - SonTek/YSI FlowTracker Acoustic Doppler Velocimeter

2009.05 Publication of the Techniques and Methods Report Book 3-Section A22, "Measuring Discharge with Acoustic Doppler Current Profilers from a Moving Boat" and associated policy and guidance for moving boat discharge measurements

2009.04 Application of FlowTracker firmware and software mounting correction factor for potential bias

2009.02 Release of WinRiver II Software (version 2.04) for Computing Streamflow from Acoustic Doppler Current Profiler Data

2008.03 Hydroacoustics Work Group - Charter, Membership, and Activities

2008.02 Upgrade for Rio Grande/Workhorse Firmware to Address Potential Bias in Discharges Measured Using Water Mode 12

2008.01 Release of WinRiver II Software (version 2.00) for Computing Streamflow from Acoustic Profiler Data

2007.01 SonTek/YSI FlowTracker firmware version 3.10 and software version 2.11 upgrades and additional policy on the use of FlowTrackers for discharge measurements

2006.04 Guidance on the use of the Loop Method** and release of "Application of the Loop Method for Correcting Acoustic Doppler Current Profiler Discharge Measurements Biased by Sediment Transport." [Revised Appendix for SIR 2006-5079]

2006.02 Quality-Assurance Plan for Discharge Measurements Using Acoustic Doppler Current Profilers

2005.08 Policy and Guidance for Archiving Electronic Discharge Measurement Data 2005.05 Guidance on the use of RD Instruments StreamPro Acoustic Doppler Profiler

2005.04 Release of WinRiver Software version 10.06 for Computing Streamflow from Acoustic Profiler Data

2004.04 Policy on the use of the FlowTracker for discharge measurements

2003.04 Release of WinRiver Software Version 10.05 for Computing Streamflow from Acoustic Profiler Data

2003.01 Discharges computed using Sontek RiverSurveyor Acoustic Doppler Current Profiler

2002.03 Release of WinRiver Software (version 10.03) for Computing Streamflow from Acoustic Profiler Data

2002.02 Policy and Technical Guidance on Discharge Measurements using Acoustic Doppler Current Profilers

2002.01 Configuration of Acoustic Profilers (RD Instruments) for Measurement of Streamflow -- National Coordination and Support for Hydroacoustic Activities

2000.03 Software for Computing Streamflow from Acoustic Profiler Data 1997.02 National Coordination and Support for ADCP Activities

1996.01 Distribution of OFR 95-701, Quality Assurance Plan for Discharge Measurements Using Broadband Acoustic Doppler Current Profilers

pg. 85 of 85