15.11.2014 Views

ssc-367 - Ship Structure Committee

ssc-367 - Ship Structure Committee

ssc-367 - Ship Structure Committee

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6. FATIGUE STRESS HISTORY MODELS<br />

Creation of the fatigue stress historymodel requires determination<br />

of the fatigueenvironmentand applicationof the environmentto the<br />

structure to produce stresses. The environment can be applied to<br />

the structure by either a spectral analysis or by a time-domain<br />

analysis. The spectral analysis derives the stress range and an<br />

average N number of cycles from the statistical properties of the<br />

stress response spectrum. A true time-domain analysis sorts the<br />

stress ranges and accumulatesthe stress range counts as the stress<br />

time history is being generated. For practical reasons a hybrid<br />

time-domain method is often used to generate stress history.<br />

6.1<br />

DETERMINATIONOF FATIGUE ENVIRONMENTS<br />

To evaluate the fatigue life of a fixed structure or a floating<br />

vessel a representativefatigue environmentmust be modeled. For a<br />

fixed structurethe fatigueenvironmentwill be the typicalwave and<br />

wind conditions for the surrounding area. For a ship the fatigue<br />

environment will be the typical environmental conditions along<br />

various routes.<br />

6.1.1 Data Sources<br />

The types of environmentaldata range from actual wave and/or wind<br />

records to recreated (hindcast)data. The wave and wind recordsmay<br />

be raw recordings (not generally available) or condensed summary<br />

reports produced by government agencies or environmental<br />

consultants. Hindcastdata are generatedby various computermodels<br />

using environmental information available for the area or nearby<br />

areas.<br />

6-1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!