3515R08 - Appendix P - Long Term Bridge Performance Protocols.pdf

APPENDIX P

LONG TERM BRIDGE PERFORMANCE

PROTOCOL

Long-Term Instrumentation

Protocol LT001

LONG-TERM INSTRUMENTATION – GENERAL

Data Collected:

• Structural performance characterization

References:

LT002 Infrastructure – Data Acquisition LT003 Infrastructure – Sensors and Cables LT004 Data Acquisition – Overview LT005 Data Acquisition – Data Format LT006 Data Acquisition – Scheduled Event LT007 Data Acquisition – Triggered Event LT009 Data Acquisition – Rainflow Histogram LT010 Sensors - Accelerometers LT011 Sensors – Bearing Movements LT012 Sensors – Displacements LT013 Sensors – Strain LT014 Sensors – Temperature LT016 Quality Assurance LT017 Instrumentation Report IP001 Instrumentation Plan – General

Process Description/Data Collection Principle:

This collection of long-term instrumentation protocols outline the steps necessary to design a Long-Term Instrumentation program for bridges.

There are four goals of the long term instrumentation program:

• Characterize traffic

• Investigate time/environmental dependent effects

• Evaluate change in response over time

• Notification of defects/cracks

Photo:

On-site Equipment:

N/A

Data Collection Methodology:

There are four goals of the long term instrumentation program:

• Characterize traffic

• Place gauges as indicated on the conceptual instrumentation plan.

• There are two options for recording ambient truck traffic strain data.

• Option 1: Triggered Event Method - Ambient traffic data will be temporarily stored and a triggered level of strain is used to filter out non-truck traffic. Strains are then permanently saved for triggered traffic events. The trigger level is set so as to filter out non-truck traffic.

Details of this method can be found in Protocol LT007.

• Option 2: Scheduled Event Method - At three hour intervals, five minutes of ambient traffic data is recorded and permanently stored. The data is analyzed as required in Protocol LT006.

• Investigate time/environmental dependent effects

• Place temperature and displacement sensors as indicated.

• This data shall be collected on a Scheduled Event Method – A single sample will be collected every 15 minutes.

• Evaluate change in response over time

• At a minimum, the gages used to characterize traffic will be used to evaluate changes in behavior of the bridge over time.

• In addition, sensors can be added per Offeror at no cast to PennDOT to evaluate other important bridge behavior parameters that may change with time including composite action, fundamental frequencies, transverse load distribution, and others.

• Notification of defects/cracks

• Upon identification of a potential defect, the system shall immediately notify designated staff for visual verification of the finding.

A long term instrumentation plan shall be submitted for approval. Format of the plan shall follow that prescribed in Protocol IP001.

The datalogger system(s) employed must accommodate all active sensors for the long term testing plan, while maintaining the required sampling rate of 100 Hz and on-board processing (see Protocol LT004). On board processing, necessary to minimize archived data, can limit sampling rates and is a significant consideration to recall when selecting a data acquisition system.

Quality assurance shall be provided by a truck of known weight which shall be compared to the results from the live load test (see Protocol LT016).

Figure 1: Sample Plan View Instrumentation-Plan (see Protocol IP001) drawing for single span bridge.

Criteria for Data Validation:

Component in Structure Breakdown:

General

Proposed Frequency and Spacing:

Next Process:

# Description Units/format Values/Accuracy

Data

Protocol LT002 Infrastructure – Data Acquisition

Data Collected:

Methods and guidelines for protection of the Data Acquisition System are presented.

References:

LT001 Long-Term Instrumentation – General LT003 Infrastructure – Sensors and Cables

Process Description/Data Collection Principle:

This protocol outlines minimum requirements for the data logger system enclosure. In all considerations, plan for a 5-year life. The following topics will be addressed:

• Enclosure

• Enclosure Mounting/Access

• Maintenance

• Vandalism

System enclosure

Data Collection Methodology:

Further explanation of the previously mentioned items is given:

Enclosure:

As a minimum, the data logger system should be housed in NEMA 4 enclosure. If the system is to be located near a flood plain or has the potential for occasional temporary submersion, a minimum of NEMA 6 is required. The size of the enclosure will depend on the data logger system and components (multiplexers, additional modules, modems, routers, etc.). When selecting a size, consideration shall be given to the need for upgrading the system and future additions to the system. Select an enclosure size that is larger than initially needed.

Access:

Once the enclosure type and size is selected, the placement of the enclosure should provide for easy access.

Suggested location include: on the abutment wall (which allows for shorter cable lengths since the data logger system is “on” the bridge), on a pier of a multi-span structure (assuming the bridge does not cross water or that the installation location is sufficiently above the water line to prevent prolonged submersion), or on a pad-mounted enclosure prepared for the purpose of housing the data logger system. Each selection has a number of pros and that need to be evaluated before making the final decision.

Protocol

Figure 2: Example of Pad-mounted DAQ Enclosure.

Figure 3: Example of Pier-mounted DAQ Enclosure.

Figure 4: Example of Abutment-mounted DAQ Enclosure.

Maintenance:

Each data logger system shall be maintained as per manufacture recommendations. The data logger system shall be visited once per year to visually inspect the components and its condition.

Vandalism:

Depending on the location, certain bridges are more susceptible to vandalism than others. Methods for preventing vandalism are to be developed by Offeror and submitted to PennDOT for review and acceptance.

Offeror is responsible for adequate insurance to cover vandalism. Where vandalism-related incidents exceed $30,000, costs above $30,000 will be shared with PennDOT.

See Protocol for Long-Term Instrumentation – General (LT001)

Protocol LT003 Infrastructure – Sensors and Cables

Data Collected:

Methods and guidelines for protection of the cabling and sensors are presented.

References:

LT002 Infrastructure – Data Acquisition

Adequate protection for cabling and sensors is an important aspect of preparing a long-term instrumentation system that will reliably and consistently provide high quality data.

Points to consider in regard to sensor and cable protection are as follows:

• Sensor Enclosure

• Conduit

Enclosures and conduit as needed

Sensor Enclosure:

Each sensor shall be protected per manufacturer recommendations to ensure a 5 year service life. One option is a NEMA 4 level enclosure. The size of the enclosure will depend on the type and quantity of sensor(s) to be housed in the enclosure. When selecting a size, consideration should be given to the need for installation, maintenance, and future additions to the enclosure. Select an enclosure size that is larger than initially needed. Some sensor manufacturers provide environmental protection for their sensors so a NEMA 4 level enclosure may not be necessary.

Conduit:

Local, state, and national codes for conduit requirements shall be followed. Offeror to provide type of conduit per RFP Work Statement. The conduit shall provide the same service life as that of the sensors and enclosure.

See Protocol for Long-Term Instrumentation – General (LT001)

Protocol LT004

DATA ACQUISITION SYSTEM - OVERVIEW

Method:

Data acquisition system requirements and standards.

References:

LT006 Data Acquisition – Scheduled Event LT007 Data Acquisition – Triggered Event LT009 Data Acquisition – Rainflow Histogram IP002 Sensor Symbols and Nomenclature

The requirements for data logger systems for long-term instrumentation are as follows.

Basic requirements for data logger systems include:

• A/D Resolution

• Measurement Type Capability

• On-Board Processing

• On-Board Memory Backup

• Communications Compatibility

• Power

Data logger

Data loggers, used for long-term instrumentation need to meet certain requirements of performance and computation to allow for accurate and reliable data collection among all bridges. Channel counts and exact mode of operation (software and hardware) are left up to the engineer designing the system to select. When choosing a system, the following base requirements shall be met.

A/D Resolution:

Minimum of a 16-bit A/D conversion accuracy shall be used. It is recommended that a 24-bit A/D conversion accuracy be considered.

Measurement Type Capability:

Sensor response can be measured using a wide range of methods including differential voltage, single-ended voltage, resistance measurement, SDI-12, RS-232, and others. The data logger system chosen shall be capable of measuring all sensors used for long-term instrumentation.

On-Board Processing:

Required on-board processing routines include; minimum, maximum, average, and rainflow histogram (Protocol LT009). Available on-board processing, or data reduction, is a quick and easy method for reducing the amount (size) of data sent from the datalogger to the archiving server. On-board processing will allow for large data files to be analyzed and reduced to highly usable forms. Some post-processing, such as modal analysis, can be too computationally intense for some data logger systems and will need to be transmitted from the datalogger in a time-series format, in engineering units (see Triggered (LT007) and Scheduled (LT006) Events).

On-Board Memory Backup:

As a minimum, the data logger shall be equipped with storage backup to allow a 48-hour period of data collection without overwriting data.

Communication Capability:

Each data logger system must have the ability to communicate with the internet to remotely transfer data to the archival site. A cellular modem, hard-line connection, or some other form of internet may be used. The connection bandwidth shall be adequate to pass data and allow for communication and remote maintenance.

Power:

Each system shall have sufficient and reliable power for continuous operation. Many systems can operate on either A/C or D/C power. In either situation, a 25% over-design of power supplied shall be provided to allow for potential expansion of the system and unforeseen large power draws.

LT006 Data Acquisition – Scheduled Event LT007 Data Acquisition – Triggered Event

Protocol LT005

DATA ACQUISITION SYSTEM - DATA FORMAT

Data Collected:

A consistent method for recording, transmitting, and storing data is provided.

References:

LT006 Data Acquisition – Scheduled Event LT007 Data Acquisition – Triggered Event LT009 Data Acquisition – Rainflow Histogram IP001 Instrumentation Plan - General

It is essential that the data be sent in a format that can be recognized.

This document explains the parts of Long-Term Instrumentation Data Format:

• Data Table(s)

• Transmission Method and Data Collection Frequency

• Code Patches to convert to Database Language

Data Tables:

Each data logger system will organize data on-board. This method will be referred to as “Data Tables” for consistency. Sensor output should be organized so that required information is stored in each data table.

There shall be a data table for the each of the following events and on-board processing routines:

• LT006 Data Acquisition – Scheduled Event

• LT007 Data Acquisition – Triggered Event

• LT009 Data Acquisition – Rainflow Histogram

Documentation of the table name and what sensors are included shall be provided.

Protocol LT006

DATA ACQUISITION SYSTEM - SCHEDULED EVENT

Data Collected:

Definitions for scheduled events are explained.

References:

LT007 Data Acquisition – Triggered Event LT009 Data Acquisition – Rainflow Histogram LT017 Reporting IP001 Instrumentation Plan - General

For sensors used to investigate temperature and time dependent effects, a slow storage rate is required. These sensors can still be sampled at high speeds, but the data storage rate can be slower. Some examples of information that fits under this category include temperature, bearing and joint movement, and strain.

On-site Equipment: N/A

A Scheduled Event is a collection of data that occurs at a set time for a set duration. To ensure that data comparison is compatible, consistent parameters are established as follows.

Sensors to Include:

Temperature sensors; strain sensors, bearing and joint movement sensors and any other structural gauge monitoring temperature and time dependent effects.

Time:

A single sample will be collected every 15 minutes, every day.

Duration:

Each scheduled event will last for one record, or a single sample.

LT017 Reporting

Protocol LT007

DATA ACQUISITION SYSTEM - TRIGGERED EVENT

Data Collected:

Definitions for triggered events provided.

References:

LT009 Data Acquisition – Rainflow Histogram

Continuous monitoring measures bridge response while vehicles cross the bridge. With the appropriate triggering mechanism in place, record the bridge response caused by large, or unusual, loading vehicles.

Definitions:

Large Vehicle:

A vehicle that causes at least 75% of the response of maximum legal load.

Triggering Mechanism:

The triggering mechanism is a strain sensor or sensors located on a heavily loaded bridge component. The live load test results are critical for establishing the trigger sensor and establishing the trigger level. The triggering mechanism and routine will likely be different for each instrumented bridge. In some cases, the triggering mechanism is a sensor or sensors (accelerometers, rotation and displacement sensors) placed to detect results from barge or vehicle impact.

How Much Data:

Collect data before (pre-trigger) and after (post-trigger) the “trigger” event. For consistency, all data logger systems shall collect 5 seconds before and 10 seconds after the triggered event.

What to do with Data:

Data collected during triggered event should be time series data and transmitted to the collection database without any post-processing. Analysis will be conducted once data has been transmitted.

Protocol LT009

DATA ACQUISITION SYSTEM - RAINFLOW HISTOGRAM

Data Collected:

Parameters for setting up a rainflow histogram are provided.

References:

ASTM E 1040-85

LT004 Data Acquisition – Overview LT006 Data Acquisition – Scheduled Event LT007 Data Acquisition – Triggered Event

Parameters for a Rainflow Histogram include:

• Bin Size

• Lower Strain Limit

• Upper Strain Limit

• Range

• Minimum Strain Amplitude

• Number of Bins

• Form

• Calculation Frequency

On-site Equipment: N/A

The rainflow-counting algorithm (also known as the "rain-flow counting method") is used in the analysis of fatigue data in order to reduce a spectrum of varying stress into a set of simple stress ranges. The algorithm shall conform to the requirements of ASTM E 1040-85.

The bin size is presented as a function of fy or f’c for steel and concrete bridges, respectively.

Steel Bridges:

• Bin size = 0.5% fy (for fy = 50 ksi, this is ~8.6 μStrain)

• Number of bins = 25

• Minimum strain amplitude = 8.2 μStrain

• Lower strain limit = 0

• Upper strain limit = 215

• Form: Reset at calculation, use total count, include outliers.

• Calculation Frequency = 24hr.

Concrete Bridges:

• Bin size= 0.15% f’c (for f’c = 6500 psi, this is ~2.1 μStrain)

• Number of Bins = 25

• Minimum strain amplitude = 4.2 μStrain

• Lower strain limit = 0

• Upper strain limit = 52.5

• Form: Reset at calculation, use total count, include outliers.

• Calculation Frequency = 24hr.

Adherence to ASTM standard

Protocol LT010

SENSORS - ACCELEROMETERS

Data Collected:

Bridge Acceleration

References:

LT001 Long-Term Instrumentation – General LT003 Infrastructure – Sensors and Cables

Acceleration, as measured on a bridge structure, is a measure of the motion of the bridge due to some loading. Typical application of acceleration from a bridge is used to determine whether the bridge has been impacted and/or modal properties of the structure. The utilization of the raw data to determine natural frequencies, mode shapes and modal damping ratios can be performed by various software applications by post processing of the time history data.

Correlation between Displacement, Velocity and Acceleration:

As a minimum, sensors shall have an adequate spatial distribution such that the first 5 modes can be distinguished and therefore monitored over time.

Dynamic variables used to define motion are position, velocity, and acceleration. The three variables are interrelated as each is a function of the other. Meaning, if s=f(t) is the position function of a particle than ds/dt = v is the instantaneous velocity (i.e., the rate of change of displacement with respect to time). The instantaneous rate of change of velocity with respect to time is acceleration, a(t) = v’(t)=s’’(t). The velocity is the derivative of the position function and that acceleration is the derivative of the velocity function, or acceleration is the second derivative of the position function. Hence, displacement (position), velocity, and acceleration are all interrelated.

A method for determining vertical displacement through velocity or acceleration data can therefore be completed. Data collected with accelerometers or velocity sensors can be integrated (working in the other direction from what is presented in the previous paragraph) to produce the displacements recorded at various locations on a bridge.

Measurement Goal:

Acceleration measurements will be measuring vertical, transverse, and longitudinal motion of the bridge. The primary goal is to notify PennDOT of bridges subject to barge impact and/or overheight vehicle impact.

Installation:

The location of the acceleration sensor should be such that the placement will not interfere with daily operations of the bridge structure.

Durability:

Sensor and cable protection shall follow the requirements of Protocol LT003.

Sensor Requirements:

The selected sensor shall meet the following requirements:

Minimum Resolution 0.05 in/sec2 (0.0001g) Minimum Sampling Speed 100 Hz

Minimum Accuracy ±0.1% Maximum Acceleration Range ±5.0g

Data is validated by comparison of initial acceleration readings to dynamic test.

Superstructure

Protocol LT011

SENSORS – BEARING MOVEMENTS

Data Collected:

Bridge rotation

References:

LT001 Long-Term Instrumentation – General LT006 Data Acquisition – Scheduled Event

The in-service behavior of supports is often different from the as-designed condition. Measurement of bearing behavior is important in understanding bridge superstructure behavior. Support conditions that are not performing as designed can cause stresses in other elements and significantly alter the properties of the bridge.

ABUTMENT

GIRDER

LVDT

LVDT

The location of additional bearings (others not shown in conceptual instrumentation plans) to be instrumented for movements shall be determined based on the live load test results, the predicted movements from the pre-test finite element model, visual inspection observations, and engineering judgment.

Instrumented bearings shall be on girders with strain sensors. Rotation sensor location and an explanation for placement of that sensor shall be provided in the instrumentation plan (see Protocol IP001). Generally, there are two types of bearings in bridges: pin or roller types. For a pinned support rotation of the girder at the bearing shall be measured. For a roller support, rotation and longitudinal translation of the girder shall be measured.

Sensor output shall be stored in the Dynamic Schedule Event, Slow Scheduled Event (LT006), Triggered Event (LT007), and Maximum Event (Peak Picking) Algorithm tables.

Displacement sensors employed must be capable of accuracy and resolution better than 0.001 inch. Selection of the type of sensor to be used is a function of bridge length, since a large portion of longitudinal displacement is a function of thermal expansion. Displacement sensors should be attached to ensure fixity throughout the test and conform to manufacturers’ recommendation and DOT requirements.

Rotations shall be measured to an accuracy of + or – 0.001 degrees.

The sensor shall be attached as close as possible to the centerline of bearing and bottom flange. Any longitudinal deviation from the bearing centerline shall be measured and reported within 1 inch. The following figures provide examples of rotation sensor installations.

Figure 5: Example installation of rotation sensor on Steel Girder Bridge.

Figure 6: : Example installation of rotation sensor on PS Concrete Girder Bridge.

Figure 7: Example installation of rotation sensor on PI CIP Concrete Box Girder Bridge.

Data Processing:

See protocols for Dynamic Scheduled Event, Slow Scheduled Event (LT006), Triggered Event (LT007), and Maximum Event (Peak Picking) Algorithm tables.

Data is validated by comparison to the live load data.

Bearing

Protocol LT012

SENSORS - DISPLACEMENTS

Data Collected:

Bridge Displacements

References:

IP001 Instrumentation Plan – General

Joint movements and crack growth due to temperature changes and time-dependent effects are an important indication of bridge behavior. Joints that are not performing as desired (“lock-up”) can significantly change bridge behavior.

Joint movement and crack growth sensor locations and an explanation for placement of the sensors shall be provided in the instrumentation plan (see Protocol IP001).

Displacement sensor output shall be stored in the Dynamic Schedule Event, Slow Scheduled Event (LT006), and Triggered Event (LT007) tables.

For the long-term instrumentation most displacement measurements will be measuring longitudinal motion, whether that be bearing movement, joint movement, or some other structural member designed to move as the bridge fluctuates with load and temperature. Displacement sensors employed must be capable of accuracy and resolution better than 0.001 inch. Selection of the type of sensor to be used is a function of bridge length, since a large portion of longitudinal displacement is a function of thermal expansion, which is greatly affected by total length. Displacement sensors should be attached to ensure fixity throughout the test and conform to manufacturers’ recommendation.

Data is validated by comparison to the finite element model or an approved alternate.

Superstructure, joint, bearing

Protocol LT013

SENSORS - STRAIN

Data Collected:

General information on how to collect and present strain information is presented.

References:

IP001 Instrumentation Plan – General LT001 Long-Term Instrumentation – General LT006 Data Acquisition – Scheduled Event LT007 Data Acquisition – Triggered Event

The magnitude of service strain in bridge girders or other primary structural components is important in understanding bridge superstructure and deck behavior and changes in strain overtime indicate a change in load distribution in the bridge superstructure. This in turn indicates a possible degradation of some part of the bridge (i.e., deck or bearings). Strains, caused by truck traffic, are measured during long-term instrumentation. Expected values of strain are determined from the live load test and the pre-test finite element model.

Wheel load distributions can be calculated from the strain values measured during testing. Strain values are measured on the bottom of girders and 1/3 of the girder depth up on the web as shown in the figures. Comparing strain values at different girder depths gives insight into the level of composite action between the bridge deck and girders.

Information from the live load test, pre-test finite element model, visual inspection, and engineering judgment shall be used to create the long-term instrumentation plan (see Protocol IP001). Strain sensor location shall be provided in the long-term instrumentation plan (see Protocol IP001). Strain sensor output shall be stored as specified in the Dynamic Schedule Event, Slow Scheduled Event (LT006), Triggered Event (LT007), Rainflow Histogram (LT009), or Maximum Event (Peak Picking) Algorithm tables.

For long-term instrumentation, the strain sample rate must be set according to protocol LT001. Additionally, strain sensors must have resolution and accuracy no greater than +/- 5 microstrain.

Installation Location – Cross-Section:

Strain sensors are attached on the bottom flange where maximum positive moment (tension strains) and negative moment (compression strains) takes place for each span. Strain sensors are located at the centerline of the web. In negative moment regions. When sensors are installed near a pier, strain sensors must be placed one girder depth, plus deck thickness, from the face of the bearing. This is to ensure data is not affected by the local effects created by the large bearing force.

Installation Location - Transverse and Longitudinal Typically, strain sensors will be placed on the bottom flange of each girder at a particular bridge cross section (i.e. 0.4L or 0.6L), following the skew. These cross sections will be selected with the aid of finite element model. This line of strain sensors shall be used to calculate strain distribution factors as outlined below.

Neutral Axis To monitor neutral axis location (NA), multiple strain sensors must be placed at various heights on a girder cross section (see picture above). The distance between the maximum strain sensor and the web sensor shall be equal to one third of the girder depth. For a steel girder bridge, the top or bottom of the bottom flange or are acceptable locations.

The following four figures provide examples of strain gauge installation for four different bridge types.

Figure 8: Example sensor installation location for PT CIP Box Girder Bridge.

Figure 9: Example of sensor installation location for Adjacent Box Girder Bridge.

Figure 10: Example of sensor installation for PS Concrete Girder Bridge.

Figure 11: Example of sensor installation for Steel Girder Bridge.

The selected gauge should meet the following specifications:

Minimum Resolution 1.0 με Minimum Sampling Speed 50 Hz.

Minimum Accuracy ±0.5% Minimum Strain Range 3000 με

Copies of the sensor calibration information, data sheet, and other pertinent technical documentation shall be submitted with the Instrumentation Plan (see Protocol IP001).

Superstructure

Protocol LT014

SENSORS – TEMPERATURE

Data Collected:

Bridge Temperature

References:

IP001 Instrumentation Plan – General LT001 Long-Term Instrumentation – General

A bridge experiences temperature variations through the seasons and throughout the day. There are two types of temperature variations that are important: (1) Average daily temperature changes and (2) Temperature gradients through the depth of the deck and girders. The expansion and contraction of the bridge plays a role in service behavior and can negatively affect bridge response. Temperature can often cause large responses in other sensors (i.e., large strains due to restraint in continuous systems).

Minimum temperature readings required for long-term instrumentation are as follows:

• The temperature gradient shall be measured at a minimum of one location adjacent to an interior girder in the bridge.

• Thermal gradient in girder with temperature sensor at the top, middle, and bottom of the girder.

• Temperature sensors at locations where strain sensors are located. Required if the sensor does not have temperature compensation or built in temperature sensor.

Temperature sensor output shall be stored in the Slow Scheduled Event table (see Protocol LT006). The output shall be one sample, every 15 minutes, as engineering units.

General

Protocol LT016

QUALITY ASSURANCE

Data Collected:

Quality Assurance

References:

Process description:

Long-term instrumentation requires significant planning, preparation, time to conduct, and investment to bring to fruition.

For this reason, it is important to ensure high data quality prior to continuous running of the system. In order to assure that monitoring results are acceptable, certain benchmarks shall be met.

Data shall be evaluated immediately (within 12 hours) of sensor installation to verify its consistency and how well it compares to the pretest finite element model and live-load (LL001) and dynamic testing. An engineer familiar with installing long-term instrumentation sensors and live load and dynamic tests will know generally what to expect from a bridge once sensor installation is complete.

As a minimum requirement of testing performance, maximum strains and deflections at instrumented locations of maximum response shall be within 10% of the live load and dynamic test results or it shall be considered invalid or not functioning properly. The project manager shall verify that all sensors are working prior to acceptance.

Protocol LT017

INSTRUMENTATION REPORT

Data Collected:

Long-Term Instrumentation Report

References:

LT001 Long-Term Instrumentation – General LT004 Data Acquisition – Overview LT005 Data Acquisition – Data Format LT006 Data Acquisition – Scheduled Event LT007 Data Acquisition – Triggered Event LT009 Data Acquisition – Rainflow Histogram LT010 Sensors – Accelerometers LT011 Sensors – Bearing Movements LT012 Sensors – Displacements LT013 Sensors – Strain LT014 Sensors – Temperature

Process description:

Following installation of the long-term instrumentation system, documentation of the entire process shall be provided in a detailed report. This report will contain:

• Details of long-term instrumentation setup (see Protocol

LT001).

• Explanation, schematic outline, and technical information for sensors and DAQ System selected.

• Results must be processed as outlined in the instrument protocols (see Protocols LT010 – LT014)

• Summary of initial results (see Protocols LT004-LT009).

• Revised Instrumentation Plan to “as-installed” condition.

Data Collection Methodology:

The following outline shall be used for the report:

• Executive Summary

• Bridge and Site Description

• Review of Pretest Finite Element Creation and Results o Present Maxima for strain, displacement, and rotation.

• Review of Live Load Test and Results

• Review of Dynamic Test and Results

• Instrumentation Plan “As-Installed”

• Sensor and DAQ System Presentation

• Infrastructure Presentation

• Initial Results o Present information required by sensor protocols o Explain excessive differences between pretest finite element, live load and dynamic test results.

o Provide sample plots of each sensor type.

o Provide explanation and plot of response for all sensors that are behaving unexpectedly.

Provide plan for correction of erroneous sensors.

• Conclusions

• References

• Appendices o Field Notes o Data Sheets o Photos (not contained in body) [may be submitted as attached CD or electronic file) o Copy of all permits