quality control.dqa

8/13/2019 Quality Control.dqa

1/36

Release 5: Revision 9

SACS

Quality Control

Quality Control

RELEASE 5.2

USERS MANUAL

ENGINEERING DYNAMICS, INC.

2113 38TH STREET

KENNER, LOUISIANA 70065

U.S.A.

No part of this document may be

reproduced in any form, in an

electronic retrieval system or

otherwise, without the prior

written permission of the publisher.

Copyright 2005 by

ENGINEERING DYNAMICS, INC.

Printed in U.S.A.


2/36


SACS

Quality Control


3/36


SACS

Quality Control

i

TABLE OF CONTENTS

1.0 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

2.0 SOFTWARE CONTROL PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.1 MODULE VERSION IDENTIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.2 IMPLEMENTATION OF UPDATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.3 MODULES RELEASE PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

3.0 SOFTWARE TESTING PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1 STATIC TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.2 SYSTEM INTEGRATION TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.3 DYNAMIC TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.4 THIRD-PARTY TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

4.0 SOFTWARE SUPPORT SERVICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

5.0 FUNCTIONAL ORGANIZATION DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1 PROGRAM DEVELOPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.2 SYSTEM INTEGRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.3 BETA TESTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.4 FINAL TESTING AND RELEASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.5 DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

6.0 Q.A. OF PROGRAM MODULES AND DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6.1 PROGRAM MODULES AND CORRESPONDING MANUALS . . . . . . . . . . . . . . . . . . . 6-1

6.2 DOCUMENTATION PAGE NUMBERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

6.3 PROGRAM DOCUMENTATION CONTENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

A.0 QUALITY ASSURANCE RELEASE INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1


4/36


SACS

Quality Control

ii


5/36


SACS

Quality Control

SECTION 1

INTRODUCTION


6/36


SACS

Quality Control


7/36


SACS

Quality Control

1-1

1.0 INTRODUCTION

This document is issued for the information of users and the potential users of the

Engineering Dynamics, Inc. (EDI) SACS Software System programs. The program

quality control topics covered in this document are Software Control Procedures, Testing

Procedures, Software Support Services, Functional Organization Description and

Documentation. The development of the quality control procedure has occurred over

many years and is intended to meet the specifications of NATO Standards

Document AQAP-13.


8/36


SACS

Quality Control

1-2


9/36


SACS

Quality Control

SECTION 2

SOFTWARE CONTROL PROCEDURES


10/36


SACS

Quality Control


11/36


SACS

Quality Control

2-1

2.0 SOFTWARE CONTROL PROCEDURES

EDI develops and maintains the SACS Software suite at its home office in Kenner,

Louisiana. The program system, comprising over twenty-five (25) interrelated program

modules, resides at EDIs on-site data processing facility which houses personal

computers running Windows 2000 and XP operating systems..

Early on in the development of the SACS System of programs EDI established

management guidelines for the control of a continuously developing software product

line. The central procedure for maintaining large-scale, multifaceted software that exists

in an environment that requires continual innovations was to maintain all versions of the

software in one set of source code. EDI has developed an internal program maintenance

system that allows this to be accomplished in a highly automated procedure. Control

procedures are described in the following sections.

2.1 MODULE VERSION IDENTIFICATION

Each program module in the SACS System is tracked throughout its life by a uniquemodule version identification number. This ID number shows three principal module

qualities. For example, in the ID #XX.YY.RR.ZZ

XX is the major release number

YY is the version number

ZZ is the build number.

Module version identifications are reported in the output listing files or, where

applicable, under the help about features.

2.2 IMPLEMENTATION OF UPDATES

All updates and modifications to SACS System modules are performed by EDI engineersand programmers at EDIs in-house data processing facility headquartered in Kenner,

Louisiana.

2.3 MODULES RELEASE PROTOCOL

Distribution of all SACS modules and major system releases are processed through the

Module Release Group at EDIs home office. Each Software release is monitored by this

office which verifies testing group clearance, machine type and operating system

compatibility, export and shipping requirements and any particular special client

requirements.

The delivery of the program system is made on optical media. Such distributions consist

of the program modules requested, any data files required by the program modules andthe necessary support software. Also included will be a series of inputs and

corresponding outputs for selected analysis models which are described in Appendix A.

These analysis models have been designed to demonstrate the various functions of the

program modules being delivered. Successful installation of the program system is

achieved when identical results are produced for these analysis models on the receiving

computer system.


12/36


SACS

Quality Control

2-2


13/36


SACS

Quality Control

SECTION 3

SOFTWARE TESTING PROCEDURES


14/36


SACS

Quality Control


15/36


SACS

Quality Control

3-1

3.0 SOFTWARE TESTING PROCEDURES

EDI maintains a comprehensive in-house testing program. The testing program processes

each newly developed or updated program module through four levels of test

verification:

Level 1 Static tests

Level 2 System integration tests

Level 3 Dynamic tests

Level 4 Third-party tests

3.1 STATIC TESTS

Static tests are carried out during the software module design and/or update phase by the

engineer/programmer in charge. These tests verify the basic functioning of the software

and its compatibility with the various language translators and computer operating

systems. Program modules which are hardware and/or firmware dependent are checked

for proper function at this time.

3.2 SYSTEM INTEGRATION TESTS

The SACS Suite of program modules have been designed to draw upon one common

input database and one common output database. All newly generated or updated

program modules are tested for compatibility with these two databases. Additionally, all

program modules are verified for compatibility of input and output format with the SACS

System as a whole.

3.3 DYNAMIC TESTS

Program modules which have cleared the Static and System Integration tests are then

made available to EDIs Engineering Consultancy group in Kenner. This group performsprogram module tests, in which test results are verified against results of completed

design projects.

3.4 THIRD-PARTY TESTS

In parallel with Dynamic testing, EDI issues pre-releases of the SACS System to a

number of third-party test sites in Brazil, Norway, France and the United States for

testing of new features and/or special requests needed on short notice.


16/36


SACS

Quality Control

3-2


17/36


SACS

Quality Control

SECTION 4

SOFTWARE SUPPORT SERVICES


18/36


SACS

Quality Control


19/36


SACS

Quality Control

4-1

4.0 SOFTWARE SUPPORT SERVICES

EDI provides an extensive software support network to supplement the SACS software

quality control measures. Clients worldwide may communicate with EDI and/or SACS

software representatives via telephone, telefax or e-mail seven days a week. The client

will speak or communicate directly with one of EDIs engineers who maintains and/or

uses the SACS System on a daily basis.

The interaction which results from this support system provides a continuous feedback of

ideas, enhancements and improvements to the SACS system and thus maintains the state-

of-the-art nature and high quality in the software product line.


20/36


SACS

Quality Control

4-2


21/36


SACS

Quality Control

SECTION 5

FUNCTIONAL ORGANIZATION

DESCRIPTION


22/36


SACS

Quality Control


23/36


SACS

Quality Control

5-1

5.0 FUNCTIONAL ORGANIZATION DESCRIPTION

EDI software development and maintenance are performed in five different phases. All

phases require at least vice-presidential approval to initiate and complete. The five phases

are listed in the following sections.

5.1 PROGRAM DEVELOPMENT

This includes conceptual development as well as incorporating corrections, enhancements

and modifications. This staff includes engineer/programmers and applied research

engineers.

5.2 SYSTEM INTEGRATION

All modifications and newly developed software are tested for conformity in internal

architecture and compatibility with existing software. All new software is given initial

testing to verify that the programs are performing according to the Program Development

guidelines. Also, any documentation changes are noted and submitted to the

Documentation Group. The programs are then submitted for Beta testing.

5.3 BETA TESTING

Testing is continued by in-house engineers. This testing is performed on existing project

data and compared to previous results from those projects. Also, outside third-party

companies participate in Beta testing by accepting pre-releases of the program to be used

on actual projects. All reports are submitted to the System Integration Group for final

evaluation.

5.4 FINAL TESTING AND RELEASE

Final testing is performed on all programs on each computer type currently supported by

EDI. Standard Master Test Data is created on EDIs quality assurance server for all

programs. These Master Tests are then performed on all other hardware releases and the

program outputs are compared to the Master Outputs from the quality assurance server.

All program releases are done in machine readable form (binary or absolute) and each

release contains a complete set of installation data and output prints, described in

Appendix A, to be used at each installation for quality assurance. Since it is impossible to

test the programs on all hardware operating systems and compiler libraries, the final

testing procedure is to be performed by the client by comparing the supplied quality test

data with the test data created by the client.

5.5 DOCUMENTATION

Documentation changes are normally made to coincide with new releases of the softwarereflecting the input from the System Integration. Documents are related to the current

release of each program as is shown in Section 6. Each document is identified by the date

of its release as shown on the title page of each document. Documents are not updated on

a page basis but are released as complete documents.


24/36


SACS

Quality Control

5-2


25/36


SACS

Quality Control

SECTION 6

Q.A. OF PROGRAM MODULES AND

DOCUMENTATION


26/36


SACS

Quality Control


27/36


SACS

Quality Control

6-1

6.0 Q.A. OF PROGRAM MODULES AND DOCUMENTATION

Individual users manuals are provided for each module of the SACS Software System.

6.1 PROGRAM MODULES AND CORRESPONDING MANUALS

SACS system users manuals are updated regularly. The following table shows the

version numbers for the released version of each of the SACS System Program modules

and the release date of the corresponding users manual.

Program Description (Name) Program Version Manual Date Manual Revision

Ansys To SACS Converter 6.0.0.1 - -

Combine Postfile Utility 6.0.0.1 2005 Release 6 Revision 0

Concrete 6.0.0.1 2005 Release 6 Revision 0

Damage Center 5.1.0.1 - -

DataGen (Data Generator) 6.0.0.1 2005 Release 6 Revision 0

Dispkey 6.0.0.1 - -

Dynamic Response Analysis 6.0.0.1 2005 Release 6 Revision 0

EditKey 6.0.0.1 - -

Eigen Vector/Value Extraction (Dynpac) 6.0.0.1 2005 Release 6 Revision 0

Element Stress and Code Check (Post or SACS IV) 6.0.0.1 2005 Release 6 Revision 0

Enhancements - 2005 Release 5.2

Environmental Load Generator (Seastate) 6.0.0.1 2005 Release 6 Revision 0

Equilibrium Check (Freebody) 6.0.0.1 2005 Release 6 Revision 0

Fatigue Damage/Life Analysis 6.0.0.1 2005 Release 6 Revision 0

Flotation & Upending Analysis 6.0.0.1 2005 Release 6 Revision 0

Global Load Analysis 6.0.0.1 2005 Release 6 Revision 0

Installation - 2005 Release 5.2

Interactive Collapse Results Viewer (Collapse View) 6.0.0.1 2005 Release 6 Revision 0

Interactive Fatigue 6.0.0.1 2005 Release 6 Revision 0

Interactive Modeler (Precede) 6.0.0.1 2005 Release 6 Revision 0

Introduction - 2005 Release 5 Revision 3

Large Deflection Analysis (SACS IV) 6.0.0.1 2005 Release 6 Revision 0

Launch Analysis 6.0.0.1 2005 Release 6 Revision 0

Listing File Converter 6.0.0.1 - -

Material Takeoff Analysis 6.0.0.1 2005 Release 6 Revision 0

Model File to PDMS Converter 6.0.0.1 - -

Model Viewer Application 6.0.0.1 - -

Motion/Stability 6.0.0.1 2005 Release 6 Revision 0

Non-Linear Element Analysis (Gap) 6.0.0.1 2005 Release 6 Revision 0

Non-Linear Plastic Analysis (Collapse) 6.0.0.1 2005 Release 6 Revision 0Pile/Soil Interaction (PSI/Pile) 6.0.0.1 2005 Release 6 Revision 0

Plot Utility (Prevue) 6.0.0.1 2005 Release 6 Revision 0

Postvue 6.0.0.1 2005 Release 6 Revision 0

Preprocessor (SACS IV) 6.0.0.1 2005 Release 6 Revision 0

Rigid Body Analysis 6.0.0.1 2005 Release 6 Revision 0

Ring 6.0.0.1 - -

SACS Executive 5.2.0.0 2005 Release 5 Revision 4

SACS Probability 6.0.0.1 - -


28/36


SACS

Quality Control

Program Description (Name) Program Version Manual Date Manual Revision

6-2

SACS to FEM converter (SACS/Femsys) 6.0.0.1 - -

SACS to SAT converter 6.0.0.1 - -

SACS to WAMIT Interface 6.0.0.1 2005 Release 6 Revision 0

SACS/MORA Interface 6.0.0.1 2005 Release 6 Revision 0

SACS to 3D-DXF model conversion 6.0.0.1 - -

SACS To Ansys Convertor 6.0.0.1 - -

SDNF Converter 6.0.0.1 - -

Single Pile Analysis (PSI/Pile) 6.0.0.1 2005 Release 6 Revision 0

Single Pile Analysis using FE (Pile3D) 6.0.0.1 2005 Release 6 Revision 0

Solver (SACS IV) 6.0.0.1 2005 Release 6 Revision 0

Strucad Converter 6.0.0.1 - -

Super Element Utility 6.0.0.1 2005 Release 6 Revision 0

Transportation Inertia Load Generator (Tow) 6.0.0.1 2005 Release 6 Revision 0

Tubular Connection Check (Joint Can) 6.0.0.1 2005 Release 6 Revision 0

Wave Response Analysis 6.0.0.1 2005 Release 6 Revision 0

6.2 DOCUMENTATION PAGE NUMBERING

The page numbering guidelines have been implemented to insure that page numbering for

each users manual is consistent. The few exceptions where the numbering is not

consistent are noted.

The general guidelines for numbering the pages of each manual are the following:

1. The beginning of each manual consists of the Title Page and the Table of

Contents. Pages are numbered with lower case Roman numerals.

2. The body of each manual is divided into sections which are numbered

numerically starting with number 1.0, 2.0, etc. Each section has a title page

which describes the section and indicates the specific section number. The

section may be divided into subsections which are numbered numerically starting

with the section number then the sub-section number. For example, the first and

second sub-sections of section 1 would be numbered 1.1 and 1.2, respectively.

Pages contained in the main body of the manual are numbered as follows:

The first part, which is preceded by a hyphen, is the section number in which the

page is found. The second part of the page number, also preceded by a hyphen, is

the page number in that section of the manual. For example, the sixth page in the

fifth section of a manual is numbered 5-6 and the following page in this section

is 5-7 .

4. The body of the manual may be followed by Appendices designated as A, B, C,etc. Pages in the appendices are numbered similar to the body except that the

section designator is an alphanumeric character corresponding to the appendix

designation. For example, the fifth page of Appendix A of a manual would be

numbered A-5.


29/36


SACS

Quality Control

6-3

6.3 PROGRAM DOCUMENTATION CONTENTS

The following table lists the number of sections, appendices and indices along with the

total number of pages in each of the SACS manuals.

Manual Name Sections Appendices Indices Pages

Collapse 6 0 0 126

Collapse View 12 0 0 64

Combine 5 0 0 62

Concrete 5 1 0 114

Data Generator 7 0 0 38

Dynamic Response 5 0 0 278

Dynpac 6 0 0 78

Enhancements 1 0 0 15

Executive 10 1 1 82

Fatigue 6 0 0 334

Flotation 6 0 0 132

Freebody 3 0 0 28

Gap 5 0 0 80

Global Load Analysis 5 0 0 124

Interactive Fatigue 11 0 0 54

Introduction to SACS Programs 3 0 0 28

Joint Can 5 0 0 98

Launch 5 0 0 122

Material Take-Off 5 0 0 70

Motion/Stability 5 0 0 120

PSI/Pile 7 0 0 210

Post 5 1 0 196Postvue 10 1 0 62

Precede 16 1 1 216

Prevue 7 1 0 36

Quality Control 6 1 0 36

Release 5.2 Enhancements 4 0 0 26


30/36


SACS

Quality Control

Manual Name Sections Appendices Indices Pages

6-4

Rigid 4 0 0 34

SACS IV 6 0 0 216

SACS/WAMIT 3 0 0 114

SACSStructural Analysis

System Installation

3 0 0 24

Seastate 8 0 0 300

Superelement 5 0 0 66

Tow 5 0 0 90

Wave Response 5 0 0 186


31/36


SACS

Quality Control

APPENDIX A

QUALITY ASSURANCE RELEASE

INFORMATION


32/36


SACS

Quality Control


33/36


SACS

Quality Control

A-1

A.0 QUALITY ASSURANCE RELEASE INFORMATION

The following is a list of installation data and output prints provided for quality assurance

testing. The final quality assurance testing is to be performed by the client by comparing

the supplied quality test data with the test data created by the client.

Demo 1. Static Topside

sacinp.demo01 - SACS IV data

saclst.demo01.std - Output listing of SACS IV run

demo01.run - SACS run file

Demo 2. Static Offshore

seainp.static.demo02 - Seastate static load data

sacinp.demo02 - SACS IV static data

jcninp.demo02 - Joint Can data for static analysis

seainp.ldf.demo02 - Seastate large deflection load data

pilinp.demo02 - Pile input data

saclst.demo02.std - Output listing of Seastate, SACS IV and Joint

Can run

ldflst.demo02.std - Output listing of large deflection analysis run

pillst.demo02.std - Output listing of single-pile analysis

demo02.run - SACS multi-file run file (runs entire demo)

static.demo02.run - Run file for static analysis

ldf.demo02.run - Run file for large deflection analysis

pile.demo02.run - Run file for single-pile analysis

Demo 3. Basic Non-Linear Add-On

sacinp.gap.demo03 - SACS IV input data for Gap analysis

gapinp.demo03 - Gap input data

sacinp.psi.demo03 - SACS IV input data for PSI analysis

psiinp.demo03 - Pile/Soil Interaction input data

gaplst.demo03.std - Output listing of nonlinear Gap analysis

psilst.demo03.std - Output listing of PSI analysis


gap.demo03.run - Run file for Gap analysis

psi.demo03.run - Run file for PSI analysis

Demo 4a. Basic Dynamic Add-On (w/Dynamic Response)

sacinp.demo04a - Seastate and SACS IV data

dyninp.demo04a - Dynpac modal analysis data

dyrinp.demo04a - Dynamic response (earthquake) data

saclst.demo04a.std - Output listing for static analysis run

dynlst.demo04a.std - Output listing for modal analysis run

dyrlst.demo04a.std - Output listing for earthquake analysis

demo04a.run - SACS multi-file run file (runs entire demo)

static.demo04a.run - Static analysis run file

dynpac.demo04a.run - Modal analysis run file

earthquake.demo04a.run - Earthquake analysis run file


34/36


SACS

Quality Control

A-2

Demo 4b. Basic Dynamic Add-On (w/Wave Response)

sacinp.demo04b - SACS IV data

seainp.mode.demo04b - Seastate modal analysis load data

seainp.wave.demo04b - Seastate wave response load data

dyninp.demo04b - Modal analysis input datawvrinp.demo04b - Wave response input data

dynlst.demo04b.std - Output listing for modal analysis run

wvrlst.demo04b.std - Output listing for wave response run

demo04b.run - SACS multi-file run file (runs entire demo)

dynpac.demo04b.run - Modal analysis run file

wave response.demo04b.run - Wave response run file

Demo 5a. Basic Dynamic Fatigue (w/Dynamic Response)

sacinp.demo05a - Seastate and SACS IV data

dyninp.demo05a - Dynpac modal analysis data

dyrinp.demo05a - Dynamic response (earthquake) data

ftginp.demo05a - Fatigue datasaclst.demo05a.std - Output listing for static analysis run

dynlst.demo05a.std - Output listing for modal analysis run

dyrlst.demo05a.std - Output listing for earthquake analysis

ftglst.demo05a.std - Output listing for fatigue analysis

demo05a.run - SACS multi-file run file (runs entire demo)

static.demo05a.run - Static analysis run file

dynpac.demo05a.run - Modal analysis run file

earthquake.demo05a.run - Earthquake analysis run file

fatigue.demo05a.run - Fatigue analysis run file

Demo 5b. Basic Dynamic Fatigue (w/Wave Response)

sacinp.demo05b - SACS IV dataseainp.mode.demo05b - Seastate modal analysis load data

seainp.wave.demo05b - Seastate wave response load data

dyninp.demo05b - Modal analysis input data

wvrinp.demo05b - Wave response input data

dynlst.demo05b.std - Output listing for modal analysis run

wvrlst.demo05b.std - Output listing for wave response run

ftglst.demo05b.std - Output listing for fatigue analysis run

demo05b.run - SACS multi-file run file (runs entire demo)

dynpac.demo05b.run - Modal analysis run file

wave response.demo05b.run - Wave response run file

fatigue.demo05b.run - Fatigue analysis run file

Demo 6. Advanced Dynamic Fatigue


seainp.mode.demo06 - Seastate modal analysis load data

seainp.fatigue.demo06 - Seastate fatigue analysis load data

dyninp.demo06 - Modal analysis input data

dyrinp.demo06 - Earthquake analysis input data

wvrinp.demo06 - Wave response input data

ftginp.demo06 - Fatigue analysis input data


35/36


SACS

Quality Control

A-3

saclst.demo06.std - Output listing for static analysis run

dynlst.demo06.std - Output listing for modal analysis run

dyrlst.demo06.std - Output listing for earthquake analysis

wvrlst.demo06.std - Output listing for wave response run

ftglst.demo06.std - Output listing for fatigue analysis rundemo06.run - SACS multi-file run file (runs entire demo)

dynpac.demo06.run - Modal analysis run file

earthquake.demo06.run - Earthquake analysis run file

wave response.demo06.run - Wave response run file

fatigue.demo06.run - Fatigue analysis run file

Demo 7. Plastic Non-Linear Add-On


sacinp.gap.demo07 - SACS IV data for nonlinear gap analysis

gapinp.demo07 - Gap analysis input data

psiinp.demo07 - Pile/Soil Interaction input data

clpinp.demo07 - Nonlinear collapse analysis input datasaclst.demo07.std - Output listing of static analysis run

gaplst.demo07.std - Output listing of Gap analysis run

psilst.demo07.std - Output listing of PSI analysis

clplst.demo07.std - Output listing of nonlinear collapse analysis


gap.demo07.run - Gap analysis run file

psi.demo07.run - Run file for PSI analysis

collapse.demo07.run - Nonlinear collapse analysis run file

Demo 8. Advanced Dynamic Add-On


seainp.demo08 - Seastate input datadyninp.demo08 - Modal analysis input data

dyrinp.demo08 - Earthquake analysis input data

wvrinp.demo08 - Wave response input data

saclst.demo08.std - Output listing for static analysis run

dynlst.demo08.std - Output listing for modal analysis run

dyrlst.demo08.std - Output listing for earthquake analysis

wvrlst.demo08.std - Output listing for wave response run


static.demo08.run - Static analysis run file

dynpac.demo08.run - Modal analysis run file

earthquake.demo08.run - Earthquake analysis run file

wave response.demo08.run - Wave response run file

Demo 9. Basic Marine Add-On


gapinp.demo09 - Gap analysis input data

towinp.demo09 - Tow analysis input data

gaplst.demo09.std - Output listing for Gap analysis run

towlst.demo09.std - Output listing for Tow analysis run



36/36

SACS

Quality Control

gap.demo09.run - Gap analysis run file

tow.demo09.run - Tow analysis run file

Demo 10. Marine Installation Add-On

sacinp.demo10 - SACS IV datafltinp.demo10 - Flotation/upending input data

lnhinp.demo10 - Launch analysis input data

fltlst.demo10.std - Output listing for flotation/upending run

lnhlst.demo10.std - Output listing for Launch analysis run


flotation.demo10.run - Flotation/upending run file

launch.demo10.run - Launch analysis run file

Demo 11. Advanced Marine Transport Add-On


fltinp.demo11 - Flotation/upending input data

lnhinp.demo11 - Launch analysis input datagapinp.demo11 - Gap analysis input data

towinp.demo11 - Tow analysis input data

trninp.demo11 - Motion/Stability analysis data

fltlst.demo11.std - Output listing for flotation/upending run

lnhlst.demo11.std - Output listing for Launch analysis run

gaplst.demo11.std - Output listing for Gap analysis run

towlst.demo11.std - Output listing for Tow analysis run

trnlst.demo11.std - Output listing for Motion/Stability analysis


flotation.demo11.run - Flotation/upending run file

launch.demo11.run - Launch analysis run file

gap.demo11.run - Gap analysis run filetow.demo11.run - Tow analysis run file

motion.demo11.run - Motion/Stability analysis run file

Demo 12. Miscellaneous

sacinp.mto.demo12 - SACS IV data for Material Take-Off analysis

mtoinp.demo12 - Material Take-Off data

sacinp.wamit.demo12 - SACS IV data for SACS to WAMIT conversion

s2winp.demo12 - SACS to WAMIT conversion data

mtolst.demo12.std - Output listing for material take-off

s2wlst.demo12.std - Output listing for SACS to WAMIT conversion


mto.demo12.run - Material Take-Off run filesacs2wamit.demo12.run - SACS to WAMIT conversion run file