Software Module Design & Test Report _33.5.7, 33-2, 33-4_ v2

STONECUTTERS BRIDGE Section 33 – Wind and Structural Health Monitoring System

(HY/2002/26)

SOFTWARE MODULE DESIGN AND TEST REPORT FOR DATA PROCESSING AND MANAGEMENT (REPORT TOOLS) OF

WIND MEASUREMENT (LOGICAL DESIGN) (PS CLAUSES 33.5, 33.5.7, APPENDIX 33-2 & 33-4)

VERSION NO : 2

Employer : Highways Department,

The Government of The Hong Kong

Special Administrative Region Engineer : Ove Arup & Partners Hong Kong Limited Contractor : Maeda-Hitachi-Yokogawa-Hsin Chong

Joint Venture (MHYHJV) Sub-contractor : Lucky Engineering Co., Ltd. (LEC)

HY/2002/26

Section 33 – Wind And Structural Health Monitoring System

Software Module Design and Test Report Stonecutters Bridge

Page 1 of 37

Table of Contents

1.INTRODUCTION .................................................................................................................................................2

1.1.PURPOSE .......................................................................................................................................................2

1.2.ABBREVIATIONS ..............................................................................................................................................2

1.3.DEFINITION.....................................................................................................................................................3

1.4.REFERENCE ...................................................................................................................................................3

2.OVERVIEW ........................................................................................................................................................4

2.1.GENERAL .......................................................................................................................................................4

2.2.CORRESPONDING SPECIFICATIONS ..................................................................................................................4

3.DATA PRE-PROCESSING ................................................................................................................................5

4.DATA POST-PROCESSING................................................................................................................................8

5.DATA REPORTING ...........................................................................................................................................10

6.MODULE TESTING...........................................................................................................................................17

7.CONCLUSION OF MODULE TESTING ...........................................................................................................18

8.REQUIRED INFORMATION..............................................................................................................................18

APPENDIX A: CALCULATION REFERENCES ..................................................................................................19

APPENDIX B: TESTING RESULTS ....................................................................................................................23

HY/2002/26



Page 2 of 37

1. Introduction

1.1. Purpose

This Software Module Design Proposal and Testing Plan is produced for Stonecutters Bridge Wind And

Structural Health Monitoring System (WASHMS) as planned in the Software Quality Assurance Plan

(SQAP) under submission CSF-OT/005786 and designed according submission CSF-OT/009188,

Software Function Design Proposal for Data Processing and Management (Report Tools) (Conceptual

Design). This proposal shall be read together with the previous submitted proposals.

This proposal delivers the module requirement and design direction for the coding of the customized

modules in according to the Functional Design Proposal and PS Clauses listed in Section 1.4 of this

proposal. It can be considered as the logical design stage in the scope of the customized modules.

1.2. Abbreviations

The following abbreviations will be sued in this document:

“Ane” Anemometer

“Acc” Accelerometer

“Bar” Barometer

“Cor-Cell” Corrosion Cell

“DAU” Data Acquisition Unit

“DPCS-1” Data Processing and Control System -1

“Dsp” Displacement Transducers or Tensio Magnetic Sensor

“FE” Finite Element

“function ID” Functional Identification Number

“GUI” Graphical User Interface

“Hyg” Hygrometer

“Rfg” Rainfall gauge

“PS33” Particular Specification Section 33

“RFI” Request-for-Information

“SFRDS-MATLAB” Software Functional Requirement and Design Specification for Bridge Operation Display Using MATLAB

“SHDMS” Structural Health Data Management System

“SHES” Structural Health Evaluation System

HY/2002/26



Page 3 of 37

“SQAP” Software Quality Assurance Plan

“Str” Strain Gauge

“Tmp” Temperature Sensor

“WIM” Weight in Motion Sensor

1.3. Definition

In this document, the following words and expressions shall have the meanings hereby assigned and

expected where the context otherwise requires:

“Engineer” Ove Arup & Partners Hong Kong Limited

“HyD” Highways Department

The Government of The Hong Kong Special Administrative Region

“Specification” Particular Specification of Contract No. HY/2002/26 – Stonecutters Bridge

“Main Contractor” Maeda – Hitachi – Yokogawa – Hsin Chong Joint Venture (MHYHJV)

“Sub Contractor” Lucky Engineering Co., Ltd (LEC) - WASHMS Sub-Contractor

“MATLAB” MATLAB is a numerical computing environment and programming language. Created by The MathWorks, Inc

“IBM DB2” DB2 is one of IBM's lines of relational database management system (data server) software products within IBM's broader Information Management Software line. The software is installed in SHDMS submitted under submission CSF-OT/006555.

“DEWESoft” A data acquisition software package created by DEWETRON

“FEMtools” A solver and platform-independent CAE program providing advanced analysis created by Dynamic Design Solution

1.4. Reference

• PS33 Clause 33.5.0-1

• PS33 Clause 33.6.5.1

• PS33 Clause 33.5.7

• PS33 Appendix 33-2 and Appendix 33-4

• Software Quality Assurance Plan (CSF-OT/005786)

• Software Functional Design Proposal (CSF-OT/009188)

HY/2002/26



Page 4 of 37

2. Overview

2.1. General

The pre-processing modules run in DAU, the post-processing modules run in DPCS-1 and the reporting

modules run in SHES are included in this proposal. The details of each customized module will be

discussed in Section 3, 4 and 5 of this proposal. The flow chat of the data movement is illustrated in Figure

1.1. For each functional step within the data flow path, they have been added an unique functional

identification number (function ID) for future referencing.

Figure 2.1 General Data Flowchart

2.2. Corresponding Specifications

According the Section 2.2 from Software Functional Design Proposal, the data flow and the required data

processing from DAU to SHES for each sensory instrument according to their sensors groups has been

described. During the Module Design, those tables have been revised base on the actually development

situation. Those input & output data flow and the function ID are referred to the tables of previous submitted

CSF-OT/9188 in details:

Sensor Groups Sensor Types DAUs

(Pre-Processing)

DPCS-1

(Post-Processing)

SHES

(Reporting Tools)

U-Ane-3D Table 1a-1 Table 1a-2 Table 1a-3

U-Ane-2D Table 1b-1 Table 1b-2 Table 1b-3

Ane

P-Ane Table 1c-1 Table 1c-2 Table 1c-3

HY/2002/26



Page 5 of 37

3. Data Pre-processing

The measured (raw) data from the SS will be under pre-processing once it recorded by DAUs. As the

module design for the function stated at Tables 2a-1, 2b-1 and 2c-1, the I/O data flow chat for anemometers

are presented in Figures 3.1a, 3.1b and 3.1c respectively. The Figure indicates the data flow from the raw

data signal to the pre-processed data, these processes will be done by the formula function tools in

DEWESoft (see Figure 3.2), which is the data acquisition software installed with DAUs.

Figure 3.1a Data Flowchart of U-Ane-3D at DAU

HY/2002/26



Page 6 of 37

Figure 3.1b Data Flowchart of U-Ane-2D at DAU

HY/2002/26



Page 7 of 37

Figure 3.1c Data Flowchart of P-Ane at DAU

HY/2002/26



Page 8 of 37

Figure 3.2 Formula setup in DEWESoft

4. Data Post-processing

The pre-processed data from DAUs will undergo post-processing at DPCS-1. As the module design for the

function stated at Tables 1a-2, 1b-2 and 1c-2, the I/O data flow chat for temperature sensors are presented

in Figures 4.1a, 4.1b and 4.1c. The Figure indicates the data flow from the pre-processed data signal to the

post-processed data, these processes have been done by the MATLAB function tools in DPCS-1, which is

an integrated software installed with DPCS-1. The post-processing will be carried out automatically every 3

hours after collected the raw data and the pre-processed data.

HY/2002/26



Page 9 of 37

Figure 4.1a Data Flowchart for U-Ane-3D at DPCS-1

Figure 4.1b Data Flowchart for U-Ane-2D at DPCS-1

HY/2002/26



Page 10 of 37

Figure 4.1c Data Flowchart for P-Ane at DPCS-1

5. Data Reporting

In accordance to PS Clauses 33.5.8, the requirement for SHES of WASHMS is for reporting the

pre-processed and post-processed results. The requirement specified as follows.

The inputs of the reporting MATLAB modules are either getting from the Historical Database, Real-Time

Database or other specified storage location. User can select the specific period of time and locations of

sensor at SHES through the web-based GUI provided by IBM DB2 of SHDMS (the GUI will be submitted

separately under the submission of module design specification of SHDMS ref: CSF-OT/009523). Then, the

selected data from SHDMS will be passed to the MATLAB modules at SHES and the reporting process will

be carried out. The overall reporting tools are utilized for generated the Survey Report, Detailed Report and

Bridge Rating Report.

The linkage between the web interface to the MATLAB modules should refer to the separate submission for

SHDMS, Report Tools Module Design Specification. The individual MATLAB modules are presented in the

Figures 5.1 to 5.11. It is noted that the MATLAB modules are no longer dependent on the sensor types, but

only on the sensor group. Thus these modules can be read in general for U-Ane-3D, U-Ane-2D and P-Ane.

HY/2002/26



Page 11 of 37

Figure 5.1 Data Flow for the MATLAB Module Mat-W001 (wind-shes-01), Mat-W002 (wind-shes-02), Mat-W003 (wind-shes-03) & Mat-W004 (wind-shes-04)

Figure 5.2 Data Flow for the MATLAB Module Mat-W005 (wind-shes-05)

HY/2002/26



Page 12 of 37



HY/2002/26



Page 13 of 37


HY/2002/26



Page 14 of 37


Total Kinetic Power(Column Vector)

Header(Cell Vector)

Plot averaged Total Kinetic Power series

Sampling Rate(Scalar)

Total Kinetic Power(Column Vector)

Averaged the power


HY/2002/26



Page 15 of 37


HY/2002/26



Page 16 of 37


HY/2002/26



Page 17 of 37

Derived force(Column Vector)

Sampling Rate of the R-data

(Scalar)

R-(Column Vector)

Sampling Rate of the force data

(Scalar)

Header(Cell Vector)

Plot force against R-


Buffering force(Column Vector)

Sampling Rate of the R-data

(Scalar)

R-(Column Vector)

Sampling Rate of the force data

(Scalar)

Header(Cell Vector)

Plot force against R-


6. Module Testing

Since the MATLAB modules will be installed in SHES and triggered by a sub-module written by Java, or by

LabVIEW during the final integration, in order to facilitate the testing and debugging processes, the

following testing plan has been created. The testing philosophy is illustrated in Figure 6.1.

HY/2002/26



Page 18 of 37

Figure 6.1 Testing Plan

The modules have been tested using the WTIFM wind data. The individual testing result has been attached

in Appendix B.

7. Conclusion of Module Testing

Based on the result plots in Appendix B, we can see the testing results are same as the results submitted

under the WTIFM bi-monthly report, if any. As the report shows the reasonable figures, we can conclude

that the overall performance of the wind modules is satisfactory.

8. Required Information

During the module development, there are several items that required additional information or advices

from the Engineer or from the sensor suppliers. A separate form of Request-for-Information ref. RFI/000914

was submitted, if appropriate. The affected items are listed as follows:

PS 33.5.7 5th row point 6: Please advice the detail expression of the formula of the ESDU Spectra.

PS 33.5.7 6th row point 6: Please advice the comparison method and the values of the response from the

design and wind tunnel testing.

HY/2002/26



Page 19 of 37

Appendix A: Calculation References

The formulas for the calculation of the monitoring parameters are referenced to the PS Appendix 33-2,

which has been quoted as follows:

Statistical Calculations

1.1 Time Name Definition

10 min Mean ∑=i

is

xTf

x 1

10 min Maximum }max{max ixx =

10 min Minimum }min{min ixx =

3 sec, 10 min Gust (Peak) min10

sec3

)}(max{)}(max{

xxabsxxabs

xGust −−

=

10 min Standard Deviation ∑ −=i

is

x xxTf

2)(1σ

10 min RMS ∑=i

is

xTf

RMS 21

Wind Calculations

1.2 The measured wind speeds shall be processed for calculating dynamic wind effects based on the dynamic characteristics specified below.

All wind speeds measured by sensors SON2 - SON11 shall have the XYZ speed of the

anemometer boom measured by ACCS1 - ACCS10 subtracted to rule out movements of

the boom. The accelerometer signal shall be integrated once to have the measured signal

in the velocity domain.

• Characteristic mean wind velocity and velocity pressure for wind

For the bridge in-service without highway load and for the bridge during construction,

the characteristic 1-hour mean wind velocity profile V(z) for wind shall be taken as

19.0

1035)( ⎟

⎠⎞

⎜⎝⎛⋅=

zzV

When the wind approach is dominated by open ocean fetch (South Westerly

directions)

When the wind is approaching over complex hilly or built-up terrain (Westerly to

HY/2002/26



Page 20 of 37

South Easterly directions) the mean wind speed profile is modified as follows

29.0

103566.0)( ⎟

⎠⎞

⎜⎝⎛⋅⋅=

zzV

The characteristic 1-hour mean wind velocity pressure q(z) shall be taken as:

)(21)( 2 zVzq ⋅⋅= ρ

• Power Spectra

The power spectra of the longitudinal (u), lateral (v) and vertical (w) turbulence

components are defined according to the von Kármán spectral model.

Along-wind component (u):

6/52

10

102

)(8.701

)(4

)(

⎥⎥⎦

⎤

⎢⎢⎣

⎡⎟⎟⎠

⎞⎜⎜⎝

⎛ ⋅⋅+

⋅

=⋅

zVfL

zVfL

fSf

u

u

u

uu

σ

Cross-wind lateral (v) and vertical (w):

6/112

10

,

2

10

,

10

,

2,

,

)(2831

)(7551

)(4

)(

⎥⎥⎦

⎤

⎢⎢⎣

⎡⎟⎟⎠

⎞⎜⎜⎝

⎛ ⋅⋅+

⎥⎥⎦

⎤

⎢⎢⎣

⎡⎟⎟⎠

⎞⎜⎜⎝

⎛ ⋅⋅+⋅

⋅

=⋅

zVfL

zVfL

zVfL

fSf

wv

wvwv

wv

wwvv

σ

where the parameters in the expression are:

i turbulence component (u, v or w)

Sii(f) Wind energy spectrum for turbulence component i

f Frequency [Hz]

σi Standard deviation of wind speed for turbulence component i

V10(z) 10 min. mean wind speed at level z

Li 45.0

50 50⎟⎠⎞

⎜⎝⎛⋅=

zLL ii

HY/2002/26



Page 21 of 37

Length scales, all wind directions :Lu50 = 160 m, Lv50 = Lu50/3, Lw50 = Lu50/6

• The length scales quoted above are derived from analysis of one typhoon

event and 6 monsoon events hitting the CT8 field measurement site from North

Easterly directions. The most significant observation is that the length scales

increases with increasing height above ground level. Preliminary wind tunnel

results indicate that the length scales does not change significantly as function

of wind direction.

• Turbulence Intensity

• The turbulence intensity I of the longitudinal (u), vertical (w) and lateral (v)

turbulence components at height z above ground are given by the following

expressions:

)(10 zVI i

iσ

=

For the along-wind Iu component the following expression can be derived

190

10

10210.

uu z

.)z(V

I ⎟⎠⎞

⎜⎝⎛⋅==

σ

Corresponding to an approach dominated by open ocean fetch (South Westerly

directions). σu is assumed to be constant with height based on Iu equal to

14.5% at 70 m height above sea level inferred from the Waglan Island data

reproduced in the review of the Structures Design Manual.

When the wind is approaching over complex hilly or built-up terrain (Westerly

to South Easterly directions) the turbulence intensity profile is modified as

follows:

29.0

10

1037.0)(

⎟⎠⎞

⎜⎝⎛⋅==

zzVI u

uσ

For vertical and lateral turbulence intensities of the wind the following is

assumed based on analysis of Typhoon data recorded at the Tsing Ma bridge:

Iv = 1.00· Iu and Iw = 0.75· Iu

HY/2002/26



Page 22 of 37

• Coherence

The coherence, which defines the statistical dependency between the turbulence

components at 2 different points, is given by the following expression:

⎟⎟⎠

⎞⎜⎜⎝

⎛ ⋅⋅−=

)(exp

10 zVfDCcoh

The parameter C, the decay factor, is equal to 8 (for lateral coherences). The parameter

D is the distance between the 2 points and f is the frequency.

In table below the values of the decay factor C for all 9 coherences is listed.

Values of the decay factor C to be used in the calculations

Lateral separation

Longitudinal separation

Vertical separation

Longitudinal turbulence component 8 2 8

Cross wind turbulence component 8 4 4

Vertical turbulence component 4 4 8

HY/2002/26



Page 23 of 37

Appendix B: Testing Results

Module ID File Name Typical Result

Satisfaction

MAT-W001 Wind_rose

Accepted

MAT-W002 Wind_rose

Accepted

HY/2002/26



Page 24 of 37

MAT-W003 Wind_rose

Accepted

MAT-W004 Wind_rose

Accepted

MAT-T005 Wind_incidence

Accepted

HY/2002/26



Page 25 of 37

HY/2002/26



Page 26 of 37

MAT-W006 Turb_inten

Accepted

HY/2002/26



Page 27 of 37

MAT-W007 Time_series_plot Accepted

HY/2002/26



Page 28 of 37

HY/2002/26



Page 29 of 37

HY/2002/26



Page 30 of 37

HY/2002/26



Page 31 of 37

HY/2002/26



Page 32 of 37

HY/2002/26



Page 33 of 37

MAT-W008 WSpectrum Accepted

HY/2002/26



Page 34 of 37

Mat-W009 TKE1

Accepted

HY/2002/26



Page 35 of 37

Mat-W010 TKE2

Accepted

HY/2002/26



Page 36 of 37

Mat-W011 Wind_contour

Accepted

Mat-W012 Wind_AVD

Accepted

Mat-W013 Wind_SF

Accepted

HY/2002/26



Page 37 of 37

Mat-W014 Wind_Dsp

Accepted

\

Software Module Design & Test Report _33.5.7, 33-2, 33-4_ v2

Documents

Transcript of Software Module Design & Test Report _33.5.7, 33-2, 33-4_ v2