01 - documentation

1

Documenting the Analysis

Selecting/Generating Reports

Many reports are available, which ones do we need?

2


“General” reports are load case independent –need to be generated at most once.


12 Load Cases X 5 reports

Most “center column” reports can be generated for each ACTIVE load case.

= 60 reports

3


“Summary” reports are special – provide a single report for all selected load cases.


Most reports have standard and extended formatted options.

4

Building the Report

• Input Information:Input Information:• Input Echo

• Describes the system• Miscellaneous Report

• Provides intermediate calculations• Warning Report

13-Feb-08 Introduction to CAESAR II and Pipe Stress Analysis

g p• Lists all error check warnings and notes

• Load Case Report• Reviews options chosen

Building the Report

• General Information:General Information:• Hanger report – step completed before load

cases can be evaluated • Basic hanger table• Hanger table with text (preferred)


5

Building the Report

• Analysis Results - Structural:Analysis Results Structural:• Displacement reports

• OPErating Cases (interferences)• SUStained Cases (sag under weight)

• Restraint reports (or summary)• OPErating Cases (“hot” restraint nozzle loads)


• OPErating Cases ( hot restraint, nozzle loads)• SUStained Cases (“cold” restraint, nozzle loads)

Building the Report

• Analysis Results - Stress:Analysis Results Stress:• Stress reports (or Code Compliance) – only

for those cases for which the active codedefines a stress type• SUStained Cases (for most codes)• EXPansion Cases (for most codes)


EXPansion Cases (for most codes)• OCCasional Cases (for most codes, if present)• OPErating Cases (only for B31.4, B31.8, BS 7159,

UKOOA, etc.)

6

Building the Report

• Analysis Results - Stress:Analysis Results Stress:• Cumulative Usage Report

• Generated locally for all selected Fatigue Casesthat may occur together


Typically not included:

• Global/Local Force Reports:Global/Local Force Reports:• Usually used for “debugging” purposes

• “Summary Reports”• Used in place of corresponding “Individual

Reports”


7

Building the Output Report


Typically the “General Reports” are first.



… followed by “Structural Reports” ...

8



…and finally the “Stress Reports”.

Report Generation


Select the desired output device.

9

Text File Example


Text file default name is <jobname.out>.

MS Word Example


Word allows font changes, graphics, highlights, etc.

10

Other forms of documentation:

• Remember, you , ycan create your own Custom Report to satisfy specific requirements.


• These can be sent to any output device.


• Graphic representations:Graphic representations:• Can print or save pictures (BMP, TIF, JPG,

HTML) of CAESAR II screen shots• Can automatically create annotated stress

isometrics with CADWorx PLANT• Can export to ISOGEN (Personal ISOGEN is


• Can export to ISOGEN (Personal ISOGEN is shipped with CAESAR II)

11


• ODBC processors:ODBC processors:• Transfer data to Access, text, or XML• Automatic or manually activated• Input and/or output data


Files – what do they hold?

• General Items:General Items:• *.FIL – units files• CAESAR.CFG – configuration file• UMAT1.BIN – user material file


12


• Piping Input:Piping Input:• *._A – piping input • *._J – static load case data• *._7 – dynamic load case• *.STR – structural input


• *.SOI – soil (underground) data


• Auxiliary Input:Auxiliary Input:• *.NEM – NEMA SM 23 (steam turbines)• *.610 – API 610 (centrifugal pumps)• *.617 – API 617 (compressor)• *.661 – API 661 (air cooled heat exchangers)


• *.HEI – Heat Exchanger Institute • *.560 – API 560 (fired heaters for refineries)

13


• Auxiliary Input (cont’d):Auxiliary Input (cont d):• *.W07, *.297 – WRC 107, 297 (Vessel)• *.ISF, *.BSF – SIF scratchpads• *.FLG – flange leakage• *.31G – B31G


• *.EJM – expansion joint rating• *.UNT – AISC unity check


• Piping output:• *._P – static output• *._Q – harmonic output• *._S – spectrum output• *._T – time history output• *._M – program generated input data


p g g p• *.OTL – i/o sequencing file• *.WRN – warning file• *.XYT – time history output, by time slice

14


• Scratch Files:• *.grd – saves grid status for the current job• *.xml – plot details for the current job• *._b – boundary condition file• *._c – element characteristic file• *._e – element connectivities


• *._n – nodal coordinate file• *._r – run control file• plus analysis files (_1, _2, _5, _6)

Files – Archiving & Transporting

• For Piping Jobs, all “._?” files are zipped into the <jobname.C2> archive.

• For Structural Jobs, all “._?” files are zipped i h j b C2S hiinto the <jobname.C2S> archive.


15

Files – Archiving & Transporting

• Other important files:Other important files: • caesar.cfg – CAESAR II configuration• umat1.bin – User modified material database• equipment files – API, WRC, NEMA, etc• spectrum files – user named for dynamics• ????.fil – user named custom units file


CAESAR II Pipe Stress Analysis Seminar

COADE Engineering Software, Inc.

Questions?

01 - documentation

Documents