{"id":178,"date":"2014-11-02T14:35:48","date_gmt":"2014-11-02T14:35:48","guid":{"rendered":"https:\/\/shiplab.hials.org\/?page_id=178"},"modified":"2014-12-30T21:30:53","modified_gmt":"2014-12-30T21:30:53","slug":"preliminary-ship-division-and-assembly","status":"publish","type":"page","link":"https:\/\/shiplab.hials.org\/?page_id=178","title":{"rendered":"A Simple Modular Approach for OSV"},"content":{"rendered":"

by Olivia S. Chaves and Fabio M. Rossi\u00a0 – Exchange\u00a0Students in Ship Design\u00a0\/ H\u00f8gskolen i \u00c5lesund\u00a0<\/em>
\n(oliviachaves@poli.ufrj.br\/fabiorossi@poli.ufrj.br), v2, Dec\u00a02014.<\/em><\/p>\n

[toc]<\/p>\n

Introduction<\/h1>\n

\u00a0A modular design consist in dividing complex systems in smaller ones, so that is easier to handle them separately. Dividing the system in modules is not only helpful for dealing complexity, but also enables parallel work and promotes innovation. The reason behind it is that modular systems have standard interfaces, which guarantee that the module can be designed independently, and afterwards they will fit each other and compound the whole system.<\/p>\n

In addition, having a system divided in modules might give us some freedom in assembling these modules. For example, since the interfaces are standard, a supposed A-module might complement a B-module, as well as a C-module. In this way, it is possible to produce a wide variety of outcomes (assemblies) from a single range of modules.<\/p>\n

In doing so, if we take an Offshore Support Vessels (OSV) as our system, we can apply this approach in many different ways. The criteria used to divide a vessel in sub-systems might be, for instance, structural, piece size, or even construction phase.
\nAfter dividing OSV in modules and assembling them, we obtain a vessel with unique characteristics that will perform some missions better than others. Therefore, we can say that a given assembly is better than another one for performing a given mission by evaluating which modules it contains.<\/p>\n

Afterwards,\u00a0a\u00a0Graph User Interface\u00a0(GUI) is proposed\u00a0in order to evaluate how prepared a given assembly is for performing a mission. The\u00a0GUI main goal\u00a0is that the user can to choose the ship’s features he\/she would like to implement on the ship’s design, and in the end a grade is given for the set of choices.<\/p>\n

Methodology<\/h1>\n

First, we have simply divided an OSV in modules, where we used a functional criteria to do so. Then, we have evaluated the relationship among these modules and a given mission, and how these modules interact with each other as well. Then, an GUI started to be elaborated. The GUI gives an idea about how modules and evaluation might be handled.<\/p>\n

The methodology workflow is:<\/p>\n

\"\"<\/p>\n

Where each step means:<\/p>\n

1. Divide Ship into Modules<\/h5>\n

This consist in spliting interconnect systems, and group them according to some rule. Having these sub-systems organized in groups means having a modular ship division.
\nThe ship division was made in a preliminary way, according to system’s functionality, where all systems related to the same function should belong to the same module.<\/p>\n

2. Mapping Modules Relations<\/h5>\n

Consist in describing how the modules interact with each other. \u201cThe mapping\u201d first approach was basically to write down suggestions about how the modules obtained on the first step might influence each other.<\/p>\n

3. Mapping Mission-Module Relationship<\/h5>\n

Consist in assessing how required each module is in a ship that should perform a given mission. This is related with the role that each module plays when the ship is operating a mission.<\/p>\n

4. Mission Performance-Grading<\/h5>\n

The mission performance-grading phase consists in giving a value for an assembly (arrangement of modules) considering\u00a0the mission that the vessel should perform. It is made through a GUI that assists the user in choosing the ship’s features that he\/she would like to implement in the design.<\/p>\n

Simple Case<\/h1>\n

Applying the methodology we have proposed, for instance, we have the following:<\/p>\n

1. Ship division:<\/h5>\n

\"\"<\/p>\n

Where we have: (a) Propulsion, located in the stern, (b) Tank\/cargo hold, at the middle (square body) and in the bow, (c) Main deck, (d) Crane, and finally (e) Accommodation, in the deckhouse located aft bow.<\/p>\n

2. Modules Relationship:<\/h5>\n

 <\/p>\n

\"1\"<\/a><\/p>\n

\n

\n

3. Mission-Module Relationship:<\/h5>\n

 <\/p>\n

\n

\n

\n

\n

\n

\"2\"<\/a><\/p>\n

\n

\n

4. Mission performance-grading:<\/h5>\n

In the mission performance grading, the value we will give is measured through numbers. The tool used to calculate this grades is a GUI that\u00a0enables the user to choose vessel mission and some of its features. Inside the GUI there are formulas that automatically release\u00a0the grade for a chosen assembly, formulas which were elaborated considering the notes presented in the matrix from step 4. However,\u00a0for now, the numbers used have no theoretical basis and are just illustrative.<\/p>\n

The GUI might be seen in the following video:<\/p>\n

<\/h3>\n

Further Steps<\/h1>\n

Now, our intention is to develop this work towards a grounded and precise grading system. In order to do that, our aim is not only\u00a0have ship modules imported from Simens NX and displayed in our GUI, but also parameterize these modules and import its properties\/attributes to use as calculation source. Therefore, grading the assemblies can be done according to modules attributes (structural, hydrodynamic and functional properties) in a more precise way, even if user changes any ship dimensions, which he\/she is allowed to do.<\/p>\n","protected":false},"excerpt":{"rendered":"

by Olivia S. Chaves and Fabio M. Rossi\u00a0 – Exchange\u00a0Students in Ship Design\u00a0\/ H\u00f8gskolen i \u00c5lesund\u00a0 (oliviachaves@poli.ufrj.br\/fabiorossi@poli.ufrj.br), v2, Dec\u00a02014. [toc] Introduction \u00a0A modular design consist in dividing complex systems in smaller ones, so that is easier to handle them separately. Dividing the system in modules is not only helpful for\u2026<\/p>\n

Continue reading<\/span><\/i><\/a> <\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"class_list":["post-178","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/shiplab.hials.org\/index.php?rest_route=\/wp\/v2\/pages\/178","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/shiplab.hials.org\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/shiplab.hials.org\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/shiplab.hials.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/shiplab.hials.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=178"}],"version-history":[{"count":10,"href":"https:\/\/shiplab.hials.org\/index.php?rest_route=\/wp\/v2\/pages\/178\/revisions"}],"predecessor-version":[{"id":339,"href":"https:\/\/shiplab.hials.org\/index.php?rest_route=\/wp\/v2\/pages\/178\/revisions\/339"}],"wp:attachment":[{"href":"https:\/\/shiplab.hials.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=178"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}