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.

general assessmentof fatiguewhile the Iatterfive sectionsprovide<br />

in-depth discussion. The objectives of the document are:<br />

●<br />

Review, assess anddocument all fatigue parametersthat maybe<br />

grouped into a set of parameters (i.e., strength models,<br />

stress history models, analysis methods, etc.)<br />

●<br />

Review, assess and document strengths and weaknesses of<br />

current fatigue analysis and design procedures in conjunction<br />

with existing codes and standards.<br />

●<br />

Documentresearchgaps andrecomnend additionalresearchbased<br />

innumerous analyticalandexperimentalwork resultspublished<br />

every year.<br />

●<br />

Recommend a guideline on fatigue avoidance strategy based on<br />

numerous variablescontributingto the uncertainty of fatigue<br />

life, on recent research results and on current practices.<br />

9<br />

Assess and discussthe accuracyof fatigue life estimationand<br />

the complexity of computation based on the implication of<br />

uncertainties associatedwith the fatigue parameters and the<br />

time and effort necessary to carry out fatigue analysis and<br />

design to various levels of complexity.<br />

1.3<br />

SCOPE<br />

The following tasks were key elements in preparation of this<br />

document.<br />

●<br />

Review and assess global fatigue analysis, including fatigue<br />

as an integral part of design effort, current industry<br />

practices, codes and standards, and the implications of<br />

fatigue damage.<br />

●<br />

Review and assess all parameters within the stress model<br />

umbrella for their relative accuracy as well as application,<br />

1“3

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

Saved successfully!

Ooh no, something went wrong!