1 / 11

The STEP to HECSALV Interface

The STEP to HECSALV Interface. David Jaramillo MARVIN Project Meeting - Patras/Greece 17th - 19th January 2000. Overview of HECSALV (1). Integrated system of programs designed for rapid salvage response The salvage features include: Analysis of free-floating & stranded conditions.

pello
Download Presentation

The STEP to HECSALV Interface

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The STEP to HECSALV Interface David JaramilloMARVIN Project Meeting - Patras/Greece17th - 19th January 2000

  2. Overview of HECSALV (1) • Integrated system of programs designed for rapid salvage response • The salvage features include: • Analysis of free-floating & stranded conditions. • Stability & Strength analysis. • Oil outflow prediction based on hydrostatic balance. • Evaluation of ballast and cargo movements as well as of tidal effects. STEP to HecSalv Interface

  3. Overview of HECSALV (2) • Standard naval architectural data entry and calculations: • Hull offset entry • Hydrostatics, bonjeans and cross curve calculations • Compartment definition • Intact, trim and stability calculations • Shear force and bending moment calculations STEP to HecSalv Interface

  4. Overview of HECSALV (3) • The system consist of 14 separate modules • The integration of the different modules is achieved through data exchange in form of files • Data flow for salvage analysis STEP to HecSalv Interface

  5. Structure of Load Case file • LC files are used to describe a “load case”, i.e. a loading condition of the analysed vessel. • They are ASCII formatted (human readable). • Structured in sections, keywords & values. • There is no official documentation of the format. • Becoming obsolete: all HECSALV input formats replaced by XML in upcoming new version. STEP to HecSalv Interface

  6. Scope and objectives of the Interface Prototype Development • Scope: • Data exchange between Ship Crew and ER-Company MEIT STEP  HECSALV • Only one direction covered by the prototype. • Objectives: • Achieve deliverable T2.2D1 (prototype interface modules). • Evaluate the MARVIN concepts for data exchange (STEP). • Validate the data models and identify problems and inconsistencies. STEP to HecSalv Interface

  7. Functionality of the Interface Prototype • Simple command line application which can be started providing one or two arguments. • Read a part 21 file containing instances of the Emergency Response Data model (this file is produced by the MEIT-STEP interface). • Write a HECSALV load case file (LC file) to be used for salvage calculations. STEP to HecSalv Interface

  8. Implementation steps (1) • Collect all required Building Blocks from the EMSA server (ship product model). • Generate Short Form (SF) of Emergency Response Data model (by hand). • Parse the SF and all other referenced EXPRESS schemas, correct errors. • Compile the SF schema, correct errors. STEP to HecSalv Interface

  9. Implementation steps (2) • Generate Long Form (LF) of the model. • Parse LF, correct errors. • Compile LF, correct errors. • Create a CDA (Central Data Administration) repository and populate it with sample data (instances) using SDAI facilities of the STEP tool. STEP to HecSalv Interface

  10. Implementation steps (3) • Generate Instance File (Part 21 Interface) • Create C++ Code (Part 23 Interface) • Implement interface application (coding) • Test application with sample part 21 file Tools used: • ProSTEP Developer Tools V5.0 • MS-Visual C++ V6.0 STEP to HecSalv Interface

  11. Future work • Incorporate feedback resulting from prototype evaluation (Task 4.1) and from further model improvements (Task 1.2) • Update interface to support XML-formatted input files of the upcoming HECSALV for Windows. • Implement transfer of recommendations and results to the MEIT. STEP to HecSalv Interface

More Related